
Ultimate access to all questions.
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 in identifying why this might be the case.
Which of the following approaches can the tech lead use to identify why the notebook is running slowly as part of the Job?
A
They can navigate to the Runs tab in the Jobs UI to immediately review the processing notebook.
B
They can navigate to the Tasks tab in the Jobs UI and click on the active run to review the processing notebook.
C
They can navigate to the Runs tab in the Jobs UI and click on the active run to review the processing notebook.
D
There is no way to determine why a Job task is running slowly.
E
They can navigate to the Tasks tab in the Jobs UI to immediately review the processing notebook.
Explanation:
The correct answer is C because:
Runs Tab vs Tasks Tab: In Databricks Jobs UI, the Runs tab shows all historical and current runs of a job. Each run contains detailed execution information for all tasks within that run.
Active Run Details: By clicking on the active run in the Runs tab, you can access:
Why other options are incorrect:
Documentation Reference: As mentioned in the text, the Databricks documentation confirms that the Runs tab provides detailed information about each run's execution, including notebook execution logs, duration, resource utilization, and error messages.
This approach allows the tech lead to investigate why the notebook is running slowly by examining the specific run's execution details, logs, and performance metrics.