Databricks-DE-Assoc Implementing CI/CD Practice Question
Why should developers avoid using 'notebook' references in production pipelines that point to the 'Shared' folder for shared development work?
⚠ Common exam trap
Candidates often underestimate the risks of the 'Shared' folder, incorrectly believing it is a valid location for production code if permissions are restricted, ignoring the need for immutable version control.
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
✓
It lacks the version control and access isolation required for production.
The 'Shared' folder is meant for collaborative development, not for hosting production-ready code. Pipelines referencing this folder are susceptible to unpredictable changes, as any developer with access can modify the code. In CI/CD, production code should reside in a controlled, versioned, and immutable location. Using the 'Shared' folder for production pipelines violates the separation of concerns and increases the risk of unauthorized or accidental changes breaking critical data workflows.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Databricks jobs cannot execute notebooks from the 'Shared' directory.
Why it's wrong here
Databricks jobs are perfectly capable of executing notebooks from the 'Shared' directory. The restriction is a best practice for production stability and governance, not a technical limitation of the job scheduler. Pipelines technically run, but they inherit significant operational and security risks by relying on non-production-hardened paths.
- ✗
The 'Shared' directory is deleted automatically every 24 hours.
Why it's wrong here
Databricks does not perform automatic deletions of notebooks in the 'Shared' workspace directory. This is not a platform behavior. The recommendation to avoid this directory for production is strictly based on the need for stable, version-controlled, and secure environments, not because the files are ephemeral or subject to cleanup.
- ✓
It lacks the version control and access isolation required for production.
Why this is correct
Production assets require strict access controls and a clear audit trail. The 'Shared' folder usually has loose permissions, allowing any user to edit the code. This creates a high risk of production instability. Proper CI/CD processes dictate that production assets are deployed to hardened, versioned folders via automated pipelines.
- ✗
Notebooks in the 'Shared' directory are limited to a smaller file size.
Why it's wrong here
There is no file size limit difference between notebooks stored in the 'Shared' folder versus those in personal or production folders. The limitation is purely organizational and related to environment management. Code quality and deployment governance are the actual reasons why 'Shared' folders should not host production code.
About these practice questions
Courseiva writes every Databricks-DE-Assoc question from scratch — 276 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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-Assoc 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-Assoc exam.