Databricks-DE-Assoc Implementing CI/CD Practice Question
A team wants to ensure that code changes to their Databricks notebooks are reviewed before being deployed to production. They use a Git repository and Databricks Repos. Which practice should they implement in their CI/CD process?
⚠ Common exam trap
Test-takers frequently confuse access control (who can edit) with change control (who can approve and merge), when code review requires a pull request workflow.
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
✓
Require pull requests with at least one approval before merging into the main branch, and trigger production deployment only after the merge.
Enforcing pull requests with approvals through branch protection rules ensures that changes are reviewed before merging. Deploying to production only after the merge ties deployment to reviewed code. This practice is essential for maintaining code quality and auditability in a CI/CD pipeline.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Allow developers to commit directly to the main branch and deploy automatically to production on every commit.
Why it's wrong here
Committing directly to main and auto-deploying bypasses code review and increases the risk of deploying untested or broken code. This contradicts the goal of ensuring changes are reviewed before production. A branch protection policy with pull requests is needed to enforce review.
- ✗
Use Databricks Repos to create a separate repository for each developer and merge changes manually in the production workspace.
Why it's wrong here
Separate repositories per developer fragment the codebase and make collaboration and review difficult. Manual merging in the production workspace is error-prone and not auditable. This approach does not provide a controlled review process and undermines CI/CD consistency.
- ✓
Require pull requests with at least one approval before merging into the main branch, and trigger production deployment only after the merge.
Why this is correct
Branch protection rules that require pull requests and approvals enforce peer review before code reaches main. Triggering production deployment after the merge ensures that only reviewed and approved code is deployed. This is a foundational CI/CD practice for controlled, auditable releases.
- ✗
Configure the production workspace to allow only workspace admins to edit notebooks, and have developers request admin assistance for each change.
Why it's wrong here
Restricting edits to admins and requiring manual intervention creates a bottleneck and does not constitute code review. It also prevents developers from using standard Git workflows. This is not a scalable or recommended practice for CI/CD; branch protection and pull requests are the correct mechanisms.
About these practice questions
This Databricks-DE-Assoc question is part of Courseiva's 276-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-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.