Databricks-DE-Pro Debugging and Deploying Practice Question
A data engineer needs to inspect the logs of a long-running Databricks job that has already completed. Where should they navigate in the Databricks UI to find the driver logs?
⚠ Common exam trap
Candidates often look in the 'Cluster' logs tab or the 'Workspace' file browser, assuming job logs are stored in the same place as cluster-level event logs or source code.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The 'Runs' tab within the specific Job's detail page.
The Job Runs view provides a comprehensive audit trail of all executions, including specific task logs and driver output. Accessing the 'Runs' tab for a specific job allows the engineer to select a historical run and view the standard output and standard error streams. This is the primary interface for post-mortem debugging and understanding the execution context of failed tasks that are no longer actively running on a cluster.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The 'Clusters' tab under the 'Event Log' section.
Why it's wrong here
The Event Log in the Clusters tab tracks infrastructure events like cluster start, stop, and node failure. It does not contain application-level logs generated by code execution, such as Spark logs or print statements from Python notebooks. Therefore, it is not the correct location for debugging notebook failures.
- ✓
The 'Runs' tab within the specific Job's detail page.
Why this is correct
The 'Runs' tab contains the history of all past job executions. By clicking into a specific run, users can access the task logs, driver logs, and Spark UI links. This is the intended UI location for inspecting logs for completed or failed jobs to determine the root cause.
- ✗
The 'Workspace' folder where the notebook is stored.
Why it's wrong here
The Workspace folder contains the source code and notebook artifacts, not the execution logs. Logs are ephemeral or stored in external storage locations associated with the cluster run, not in the file system where the notebook code resides. Navigating here will not provide any information about past job runs.
- ✗
The 'SQL Warehouses' monitoring dashboard.
Why it's wrong here
SQL Warehouses are dedicated to executing SQL queries. While they have their own monitoring and query history, they are not the location for managing or inspecting logs for general-purpose notebook-based Databricks Jobs. The job run history is managed separately under the 'Workflows' or 'Jobs' interface.
About these practice questions
One of 267 original Databricks-DE-Pro practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Pro practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Pro exam.