CERTIFIED-DATA-ANALYST-ASSOCIATE Question #70: Real Exam Question with Answer & Explanation

Question

Query History provides Databricks SQL users with a lot of benefits. A data analyst has been asked to share all of these benefits with their team as part of a training exercise. One of the benefit statements the analyst provided to their team is incorrect. Which statement about Query History is incorrect?

Options

• AIt can be used to view the query plan of queries that have run.
• BIt can be used to debug queries.
• CIt can be used to automate query execution on multiple warehouses (formerly endpoints).
• DIt can be used to troubleshoot slow running queries.

Explanation

Option C is incorrect because Query History is a passive, read-only monitoring and diagnostic tool - it records and displays information about queries that have already run, but it has no capability to schedule or automate query execution across warehouses. That kind of automation is handled by separate tools like Databricks Workflows or the REST API.

Why the distractors are wrong (i.e., why A, B, and D are true statements):

• A is correct: Query History does let you inspect the query plan (logical/physical execution plan) for completed queries.
• B is correct: By exposing error messages, execution details, and row counts, Query History is a standard debugging resource.
• D is correct: Duration, queue time, and resource metrics in Query History are specifically designed for diagnosing slow queries.

Memory tip: Think of Query History as a "flight recorder" - it passively captures what already happened so you can review and diagnose it, but it cannot fly the plane. Anything that triggers or schedules execution lives elsewhere in the Databricks ecosystem.

No community discussion yet for this question.