DP-750 Certification Practice Question #85

Question

Your team uses an Azure Databricks Git folder under `/Workspace/Users/<email>/` to develop notebooks against a shared GitHub repository. A developer finishes a notebook, commits it, and pushes it to a feature branch. After the pull request is merged into `main`, a manager claims that the merged notebook is now automatically live in the production workspace.

**Proposed solution:** Committing and pushing notebooks from a user-level Git folder, and merging the pull request into the `main` branch on the Git provider, automatically deploys those notebooks into the production Databricks workspace with no further action required.

**Does this solution meet the goal?**

Accepted Answer

Committing and pushing from a user-level Git folder only updates the remote Git repository, and merging the pull request only updates the `main` branch — neither action touches the production Databricks workspace. A production Git folder (or a bundle deployment) is a separate, admin-owned location that must be brought up to date by automation: external CI/CD such as GitHub Actions that pulls the latest commits on merge, or a scheduled job that calls the Repos API. Without that deployment step, the merged notebook is not automatically live in production, so the proposed solution does not meet the goal.

More DP-750 practice questions