Databricks Certified Data Engineer - Associate
Get started today
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?
Real Exam
Community
KKeng
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:
Explanation
In Databricks Jobs, when you need to investigate why a notebook is running slowly during an active job run, you should:
- Navigate to the Runs tab in the Jobs UI
- Click on the active run to access detailed information about that specific execution
- From there, you can review the processing notebook and examine metrics, logs, and performance data
Why option C is correct:
- The Runs tab shows all job executions (both historical and current)
- Clicking on an active run provides real-time insights into the running tasks
- You can view Spark UI, logs, and other diagnostic information for the specific notebook task
Why other options are incorrect:
- Option A: You cannot "immediately review" from the Runs tab without clicking on the specific run
- Option B: The Tasks tab shows task definitions, not active run details
- Option D: This is incorrect - Databricks provides extensive monitoring capabilities
- Option E: The Tasks tab shows task configurations, not real-time execution data
This approach allows the tech lead to access detailed execution metrics, Spark UI, driver logs, and other diagnostic information to identify performance bottlenecks in the notebook.
Comments
Loading comments...