A single Job runs two notebooks as two separate tasks. A data engineer has noticed that one of the notebooks is running slowly in the Job's current run. The data engineer asks a tech lead for help…

Question

Options

• AThey can navigate to the Runs tab in the Jobs UI to immediately review the processing notebook.
• BThey can navigate to the Tasks tab in the Jobs UI and click on the active run to review the
• CThey can navigate to the Runs tab in the Jobs UI and click on the active run to review the
• DThere is no way to determine why a Job task is running slowly.
• EThey can navigate to the Tasks tab in the Jobs UI to immediately review the processing notebook.

• B
  5% (1)
• C
  90% (18)
• E
  5% (1)

Explanation

In Databricks Jobs UI, the Runs tab shows the history and currently active runs of a Job. By clicking on the active run, the tech lead can drill into run details, including per-task status, logs, Spark UI links, and performance metrics for each notebook task. This allows them to investigate why a specific notebook is running slowly. The Tasks tab (options B/E) shows task configuration, not live run diagnostics. Option A suggests reviewing the notebook immediately from the Runs tab without clicking into the run, which does not provide detailed performance information.

No community discussion yet for this question.