Home / Data Engineer Associate / Objective 6.2

Domain 6: Troubleshooting, Monitoring, and Optimization · 10% of the exam · Full exam outline

6.2 Use the Lakeflow Jobs UI to monitor pipeline health by interpreting job statuses, viewing DAG-based task graphs to spot upstream blockers, and tracking pipeline run times and failure rates.

Practice questions

Question 1easy

A platform lead wants one place in the Lakeflow Jobs UI that shows which error types caused the most failed job runs across the workspace over the last two days. Where is this summarized?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

The Timeline view is useful for finding slow tasks and overlap inside one run, but it covers a single run, not error trends across all jobs.

The Runs tab under Jobs & Pipelines includes a Top 5 error types table for the selected time range, listing the most frequent error types across runs, which is the workspace-wide summary the lead needs.

Exporting to HTML preserves one notebook run's source and outputs. It produces no cross-job error summary.

Lineage shows upstream and downstream Unity Catalog tables for a job. It does not aggregate run errors.

Question 2medium

An hourly job has started finishing late. Hovering over a recent run's Duration shows most of the time spent in the Queued phase, while time in the Running phase is unchanged. Each hourly run sometimes overlaps with the next one. What should the engineer change first?

Included in Master: master every domain.See plans