Databricks-DE-Pro Monitoring and Alerting Practice Question
An engineer notices that a SQL warehouse is frequently hitting 'Max Concurrency' limits. Which log should they consult to identify which specific queries are consuming most of the warehouse resources?
⚠ Common exam trap
Candidates often choose 'Cluster Logs' to investigate SQL concurrency, missing that 'Query History' is the purpose-built system table for tracking resource consumption by specific SQL queries.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Query history system table
The 'query_history' system table is the primary resource for analyzing query performance and resource consumption. By querying this table, engineers can attribute resource usage to specific users, notebooks, or warehouses. This is essential for troubleshooting concurrency bottlenecks, enabling teams to optimize expensive queries or adjust warehouse sizing to meet demand without impacting overall system performance or user productivity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Cluster event logs
Why it's wrong here
Cluster event logs record lifecycle events such as node starts, autoscaling and configuration changes, not per-query resource consumption. They suit diagnosing cluster-level failures. Identifying concurrency-heavy queries requires the SQL warehouse query history, which shows duration and resource usage per statement.
- ✓
Query history system table
Why this is correct
The query history system table provides comprehensive details about every query executed, including the duration, user, warehouse, and CPU/memory footprint. It is the most appropriate source for identifying heavy queries causing concurrency limits to be reached.
- ✗
Job run history logs
Why it's wrong here
Job run history logs are scoped to job tasks and do not capture individual queries submitted through the SQL warehouse interface by users or BI tools. Therefore, they are insufficient for debugging concurrency issues on SQL warehouses.
- ✗
Delta table access logs
Why it's wrong here
These logs are primarily used for security auditing to see who has accessed specific data files. They lack the performance and execution plan details necessary to debug compute resource consumption or concurrency bottlenecks in a SQL warehouse.
About these practice questions
This Databricks-DE-Pro question is part of Courseiva's 267-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Pro practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Pro exam.