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?
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.