Answer: They can navigate to the Runs tab in the Jobs UI and click on the active run to review the processing notebook.

## Explanation In Databricks, when you need to investigate why a notebook is running slowly as part of a Job, you should: 1. **Navigate to the Runs tab in the Jobs UI** - This shows all the runs of the job 2. **Click on the active run** - This allows you to see the details of the current execution 3. **Review the processing notebook** - From there, you can access the notebook execution details, logs, and metrics to identify performance issues **Why option C is correct:** - The Runs tab shows all job executions (historical and current) - Clicking on the active run gives you access to the specific execution details - You can then examine the notebook's execution, view logs, check cluster metrics, and identify bottlenecks **Why other options are incorrect:** - **A**: You cannot "immediately review" from the Runs tab without clicking on the specific run - **B**: The Tasks tab shows task configurations, not active run details for troubleshooting performance - **D**: This is incorrect - Databricks provides extensive monitoring and debugging capabilities - **E**: You cannot "immediately review" from the Tasks tab; you need to navigate to the specific run **Key Databricks UI Navigation:** 1. Jobs → Select your job → Runs tab → Click on active run → View task details and logs 2. From there, you can access Spark UI, driver logs, and notebook execution details to diagnose performance issues.

Author: Keng Suppaseth