Databricks-DE-Pro Monitoring and Alerting Practice Question
A data engineer supports a Delta Live Tables pipeline that ingests streaming data from Kafka. The pipeline sometimes experiences latency spikes, and the engineer needs to determine whether the bottleneck is in the ingestion stage or in downstream transformations. They want to use built-in observability without adding external tooling. Which approach provides the most direct insight into per-stage event processing times within the DLT pipeline?
⚠ Common exam trap
The trap here is assuming that cluster CPU metrics or Spark UI query plans can reveal DLT stage-level timing, when only the event log exposes flow_progress details.
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
✓
Enable the event log and query the event_log table for flow_progress events to inspect stage-level metrics such as backlog and processing time.
The event log is the built-in observability mechanism for Delta Live Tables. By querying flow_progress events, the engineer gains stage-level metrics that directly show backlog and processing time for each flow. This allows precise identification of whether ingestion or transformation is the source of latency, without deploying external monitoring tools.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure Databricks SQL alerts on the pipeline's target tables to detect latency by comparing row counts over time.
Why it's wrong here
SQL alerts on target tables can indicate throughput anomalies, but they measure end results rather than internal stage timings. They cannot isolate whether delay originates in ingestion or transformation, and they add latency because alerts run on a schedule. This approach is indirect and not suitable for per-stage diagnosis.
- ✗
Monitor cluster CPU utilization in the Clusters UI and correlate spikes with pipeline run times.
Why it's wrong here
Cluster CPU metrics show resource consumption but do not attribute time to specific DLT flow stages. High CPU could result from either ingestion or transformation, so this method cannot distinguish the bottleneck. It also lacks the granularity of per-stage event metrics available in the event log.
- ✗
Use the Spark UI's SQL tab to inspect query plans for each streaming micro-batch.
Why it's wrong here
The Spark UI SQL tab shows query plans for completed batches, but it does not expose DLT flow stage-level metrics such as backlog or per-stage processing time. It is useful for diagnosing shuffle or join inefficiencies, yet it cannot distinguish ingestion from downstream transformation bottlenecks in the DLT pipeline context.
- ✓
Enable the event log and query the event_log table for flow_progress events to inspect stage-level metrics such as backlog and processing time.
Why this is correct
The DLT event log captures flow_progress events that include stage-level metrics, including backlog bytes and records, as well as processing time. Querying the event_log table directly surfaces these metrics without external tools, allowing the engineer to compare ingestion versus transformation stages and pinpoint where latency accumulates.
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.