Databricks-DE-Pro Debugging and Deploying Practice Question
A data engineer is deploying a Databricks Asset Bundle (DAB) that defines a job with a notebook task. The bundle validates locally, but deployment fails with 'Error: cannot find notebook at path /Workspace/Users/dev@example.com/pipeline/ingest'. The engineer confirms the notebook exists in the workspace at that exact path. Which action should the engineer take to resolve the deployment failure?
⚠ Common exam trap
The trap here is assuming that because the notebook exists in the workspace, the bundle can reference it directly; bundles require relative paths within the sync root.
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
✓
Ensure the notebook path in the bundle configuration is relative to the bundle root and that the sync root includes the notebook
Databricks Asset Bundles synchronize files from the bundle root to the workspace. Notebook paths must be relative to the bundle root and included in the sync. An absolute or incorrectly rooted path causes deployment to fail even if the file exists in the workspace, because the bundle cannot map it to a synchronized file.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add the spark.databricks.workspace.path Spark config to the job cluster
Why it's wrong here
There is no Spark configuration that resolves bundle notebook paths. Bundle path resolution happens during deployment, before Spark starts. Adding a Spark config would not affect how the bundle locates the notebook file. The engineer must correct the bundle's file references and sync configuration instead.
- ✓
Ensure the notebook path in the bundle configuration is relative to the bundle root and that the sync root includes the notebook
Why this is correct
DABs resolve notebook paths relative to the bundle root and synchronize files to the workspace. If the path is absolute or points outside the sync root, deployment cannot find it. Making the path relative and confirming the sync root includes the notebook ensures the file is uploaded and the job references the correct workspace location.
- ✗
Convert the notebook task to a Python wheel task
Why it's wrong here
Converting to a Python wheel task changes the task type and requires building and uploading a wheel. While wheel tasks are useful for production, this change does not address the underlying path resolution error. The bundle would still need correct file references. The engineer should fix the notebook path configuration rather than change the task type.
- ✗
Change the notebook task to use a Git source instead of a workspace path
Why it's wrong here
Switching to a Git source changes the deployment model and may not be desired. The error indicates a path resolution issue within the bundle, not an inherent problem with workspace paths. Git sources are valid but require additional configuration and are not the direct fix for a path that the bundle cannot resolve. The engineer should first ensure the bundle's sync root and relative paths are correct.
Visual reference
About these practice questions
This Databricks-DE-Pro question is part of Courseiva's 267-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.