Home / DE Professional practice test / Debugging and Deploying / Question

Databricks Data Engineer Professional · free practice question

A data engineer needs to identify which specific tasks within a multi-task Databricks job run failed, along with the start time, end time, and result state for…

Exam-style question on Debugging and Deploying from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Debugging and Deploying Medium

A data engineer needs to identify which specific tasks within a multi-task Databricks job run failed, along with the start time, end time, and result state for each task in that run. They want to query this information programmatically using SQL on a Unity Catalog-enabled workspace. Which system table should they query?

  1. Asystem.lakeflow.job_run_timeline
  2. Bsystem.compute.warehouse_events
  3. Csystem.lakeflow.job_task_run_timeline
  4. Dsystem.lakeflow.pipeline_update_timeline
Answer & explanation

Correct answer: C

WHY C: The system.lakeflow.job_task_run_timeline table in the Unity Catalog system catalog records per-task execution details for each job run, including the task key, start time, end time, result_state, and other identifying fields. It is the table to use when troubleshooting which tasks within a multi-task job succeeded, failed, or were skipped. System tables in the system catalog are Databricks-managed, read-only tables that require Unity Catalog; access requires USE CATALOG, USE SCHEMA and SELECT (account admins have access by default), and data is retained for 365 days in most system tables. Other system tables answer other questions: system.billing.usage records DBU cost and usage by product, SKU, and workspace for cost analysis and chargeback; system.compute.node_timeline records node-level metrics for diagnosing cluster scaling and node problems; system.access.audit records audit events (who accessed what, when, from which workspace) for security and compliance.

WHY NOT A: system.lakeflow.job_run_timeline records start time, end time and result state at the job-run level. It has one timeline per run, not per task, so it does not show which tasks inside the run failed.

WHY NOT B: system.compute.warehouse_events records SQL warehouse events such as starting, stopping and scaling. It holds compute lifecycle data, not job task start times, end times, or result states.

WHY NOT D: system.lakeflow.pipeline_update_timeline tracks updates of Lakeflow Spark Declarative Pipelines. It describes pipeline updates rather than the tasks of a Lakeflow Jobs run.

Take the full DE Professional practice test free →

Would you pass today?

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

Start the free test →