An engineer needs to list the current tables and views inside one schema with results that reflect objects created moments ago and with no metadata delay. They are deciding between querying the ACCOUNT_USAGE schema and the INFORMATION_SCHEMA. Which source best satisfies the need for real-time, low-latency metadata about the objects in that schema?
- AINFORMATION_SCHEMA, because it exposes live, low-latency metadata about current objects in a database and so reflects tables and views created moments ago Correct
- BACCOUNT_USAGE, because its views are updated in real time with no latency and therefore always reflect objects created moments ago across every database in the account
- CACCOUNT_USAGE, because it retains dropped objects and long history, making it the only source able to return the up-to-the-second list of current objects in the schema
- DINFORMATION_SCHEMA, because it stores a full year of account-wide history and therefore returns the freshest possible list of current objects in the schema
Why A is correct: INFORMATION_SCHEMA provides real-time metadata about the current objects in a database with effectively no latency, so it immediately reflects newly created tables and views, matching the requirement.
Why B is wrong: ACCOUNT_USAGE views carry a built-in latency that can run to a couple of hours, so they will not immediately reflect objects created moments ago, which fails the real-time requirement.
Why C is wrong: Retaining dropped objects and long history is a strength for auditing, but the latency on ACCOUNT_USAGE means it is not up to the second, so it does not satisfy the low-latency need described.
Why D is wrong: INFORMATION_SCHEMA is current and low latency but it does not store a long account-wide history, so the stated reason is wrong even though this source is otherwise close.