DEA-C02 · Question #101
A Data Engineer needs to monitor data usage patterns, performance metrics, and query efficiency to optimize the data workloads in a Snowflake account. The Engineer needs insights into long-running…
The correct answer is B. Use the view to analyze query performance. E. Use the SNOWFLAKE.ACCOUNT_USAGE.ACCESS_HISTORY view to track access patterns. F. Use the SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY view to monitor. B (QUERY_HISTORY), E (ACCESS_HISTORY), and F (WAREHOUSE_METERING_HISTORY) together directly map to the three core requirements: query performance analysis, access pattern tracking, and warehouse resource monitoring. QUERY_HISTORY surfaces long-running queries and execution…
Question
A Data Engineer needs to monitor data usage patterns, performance metrics, and query efficiency to optimize the data workloads in a Snowflake account. The Engineer needs insights into long-running queries, frequently accessed tables, and warehouse resource utilization while also tracking user activities and ensuring compliance with governance policies. Which combination of views should the Engineer use to meet these requirements? (Choose three.)
Options
- ASNOWFLAKE.ACCOUNT_USAGE.OBJECT_DEPENDENCIES view to track dependencies between
- BUse the view to analyze query performance.
- CUse the SNOWFLAKE.ACCOUNT_USAGE.SCHEMA_PRIVILEGES view to ensure compliance with
- DUse the view to analyze
- EUse the SNOWFLAKE.ACCOUNT_USAGE.ACCESS_HISTORY view to track access patterns.
- FUse the SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY view to monitor
How the community answered
(55 responses)- A5% (3)
- B82% (45)
- C11% (6)
- D2% (1)
Explanation
B (QUERY_HISTORY), E (ACCESS_HISTORY), and F (WAREHOUSE_METERING_HISTORY) together directly map to the three core requirements: query performance analysis, access pattern tracking, and warehouse resource monitoring. QUERY_HISTORY surfaces long-running queries and execution details; ACCESS_HISTORY logs which users accessed which tables and when, satisfying both the "frequently accessed tables" and governance/compliance requirements; and WAREHOUSE_METERING_HISTORY tracks credit consumption and resource utilization per warehouse.
Why the distractors are wrong:
- A (OBJECT_DEPENDENCIES) shows relationships between database objects (e.g., view depends on table) - useful for impact analysis, but irrelevant to performance or compliance monitoring.
- C (SCHEMA_PRIVILEGES) shows granted privileges at the schema level, but for actual access compliance you need ACCESS_HISTORY, which captures what data was read/written at runtime, not just what was permitted.
- D is truncated and incomplete in the question stem, making it untestable - but its incompleteness itself signals it's a distractor.
Memory tip: Think "Q-A-W = Query, Access, Warehouse" - the three pillars of Snowflake operational visibility. If a question asks about what ran, who touched what, and what it cost, those three views are your answer.
Topics
Community Discussion
No community discussion yet for this question.