Data-Engineer-Associate - Implementing CI/CD (10% of the exam) - Section 5.1

Manage the code development workflow in the workspace UI, including branches in Databricks Git Folders, committing, pushing and creating pull requests.

Clone a remote repository into a Databricks Git Folder (formerly Databricks Repos), create and switch branches, commit and push changes, and open a pull request through the Git integration. Recognise which Git operations happen in the workspace and which belong in the Git provider.

Databricks Git Foldersbranchingcommit and pushpull requestsGit provider integration

Practice question for this objective

Free sampleImplementing CI/CDmedium

A data engineer has finished work on a feature branch inside a Databricks Git folder linked to a hosted Git provider. The team requires the change to be reviewed before it reaches the main branch. Which sequence reflects how the workspace UI and the Git provider divide that work?

ACommit and push the branch from the Git folder dialog, then open, review and merge the pull request in the linked Git provider, which the dialog links out to. Correct
BPush the branch from the Git folder dialog and then run a merge command in a notebook cell, so that the branch is combined into main from inside the workspace.
CCreate the pull request from the Git folder dialog, which raises the request inside the workspace and merges the branch as soon as a reviewer approves it there.
DAsk a workspace administrator to merge the branch from the admin settings page, because branches in Databricks Git Folders are governed at the account level.

Databricks Git Folders performs branch, commit and push operations, while pull request review and merge happen in the linked Git provider. A Git folder is a working copy of a remote repository inside the workspace. Its dialog can create a branch, stage a commit and push that commit to the remote, but the repository's review workflow is a feature of the hosting provider, so the pull request is opened and merged there and the workspace simply links out to it.

Why A is correct: Correct, because Databricks Git Folders handles the branch, commit and push, while the pull request itself lives in the provider that hosts the repository.

Why B is wrong: It is tempting because notebooks can run shell commands, but a Git folder is not a general command line checkout and merging this way bypasses the review the team requires.

Why C is wrong: Plausible because the dialog does mention pull requests, but the workspace hosts no review surface of its own; approval and merge belong to the linked provider.

Why D is wrong: Tempting for teams used to central control, but admin settings govern the Git provider integration and credentials, not the branch history of a linked repository.

See more Data-Engineer-Associate practice questions, answers explained.

Exam traps in Implementing CI/CD

Answers that look right on this material and are not. Each one is a distractor from a different question in the Data-Engineer-Associate bank for this domain.

The Git dialog merges the feature branch into main inside the workspace once the required reviewers have added their approval in the dialog, and it then pushes the merge commit to the provider.
Why it is wrong: It sounds reasonable because the dialog does handle branches, commits and pushes, but Databricks does not host code review, and approvals are recorded by the provider.
Restart the all purpose cluster that the notebooks are attached to, because the workspace serves notebook source from the compute layer and the merged revision is only picked up on the next cluster start.
Why it is wrong: Restarting compute is a familiar remedy for stale library state, which makes it tempting, but notebook source in a Git Folder is workspace content and has nothing to do with cluster lifecycle.
Set the Git Folder's workspace permissions to read only for the engineering group, so that the branch checked out in that folder cannot be moved between production runs.
Why it is wrong: Tempting because it does stop casual branch switching, but it also stops the engineers developing there, which the requirement forbids, and it still leaves production reading a mutable workspace copy rather than a reviewed branch.

Examworthy is not affiliated with or endorsed by Databricks. Original, blueprint-aligned practice material only.