The correct answer is C. The ACCOUNT_USAGE schema does not provide real-time results .
The ACCOUNT_USAGE schema contains historical metadata and usage information for the Snowflake account, but its views have latency. This means recently executed queries may not appear immediately.
Corrected wording:
The object is typically referred to as the QUERY_HISTORY view in the ACCOUNT_USAGE schema, not QUERY_HISTORY_VIEW.
Why C is correct:
If queries ran only 10 minutes ago, they may not yet appear in SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY because ACCOUNT_USAGE views are not real-time. For more immediate query history, users can use the INFORMATION_SCHEMA.QUERY_HISTORY table function, subject to its scope and retention limits.
Why the other options are incorrect:
A. Running queries on a multi-cluster warehouse does not prevent query history from being recorded.
B. Queries using the result cache can still appear in query history.
D. If the user lacked privileges, they would generally be unable to query the view or would have limited visibility, but the key clue is that the queries ran in the past 10 minutes.
Official Snowflake documentation reference:
Snowflake documentation states that ACCOUNT_USAGE views can have latency and should not be expected to return real-time data.
[Reference: Snowflake Documentation — ACCOUNT_USAGE schema; Snowflake Documentation — QUERY_HISTORY view; Snowflake Documentation — INFORMATION_SCHEMA.QUERY_HISTORY; SnowPro Core Study Guide — Account Usage and Monitoring., ========================]
