Home / Data Analyst practice test / Analyzing Queries / Question

Databricks Data Analyst Associate · free practice question

A data analyst wants to review all queries run against a specific SQL warehouse by all users over the past 7 days, including failed queries, to identify…

Exam-style question on Analyzing Queries from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Analyzing Queries

A data analyst wants to review all queries run against a specific SQL warehouse by all users over the past 7 days, including failed queries, to identify problematic patterns. Which Databricks feature provides this team-wide query history visibility?

  1. AThe Query History page — lists the analyst's own queries by default and also other users' queries when the analyst holds at least CAN VIEW permission on the SQL warehouse that ran those queries
  2. BDESCRIBE HISTORY table_name — returns the Delta transaction log for a table, listing the user, timestamp and statement of each read and write that a SQL warehouse ran against that table
  3. CThe system table system.query.history — readable by any workspace user without grants, it stores the analyst's own statements per warehouse and leaves out queries submitted by other users
  4. DThe Spark event log fetched through the Clusters API — returns the driver and executor events of the SQL warehouse as JSON, with a structured row per query giving its user, status and duration
  5. EThe audit log delivered to cloud storage — captures query executions at the account level and is queryable from the SQL editor by any analyst as soon as an account admin enables log delivery
Answer & explanation

Correct answer: A

WHY A: The Query History sidebar page shows the queries the current user ran, and also shows queries from other users if the analyst has at least CAN VIEW permission on the SQL warehouse that executed them. That gives cross-user visibility within the warehouse's scope, including failed queries.

WHY NOT B: DESCRIBE HISTORY covers Delta write transactions (INSERT, UPDATE, DELETE, MERGE, OPTIMIZE) on one table; it does not record read-only SELECT executions and is not a warehouse-wide query history.

WHY NOT C: system.query.history holds account-wide query history, but it is admin-restricted by default and regular users need explicit grants; it is not limited to the analyst's own statements, and it is not the primary recommended tool for a regular analyst reviewing warehouse queries.

WHY NOT D: Spark event logs are raw, low-level driver and executor events that need manual parsing; they do not provide the structured query-level metadata available through the Query History UI or API.

WHY NOT E: Audit logs are a governance mechanism configured at the account level by an admin; they are not directly queryable from the SQL editor without additional ETL ingestion and parsing.

Take the full Data Analyst practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Analyst Associate practice test. Take it and get a section-by-section score.

Start the free test →