Home / DE Associate practice test / Implementing CI/CD / Question

Databricks Data Engineer Associate · free practice question

A data engineer wants to develop pipeline code in an isolated branch inside the Databricks workspace, commit changes, and open a pull request for review before…

Exam-style question on Implementing CI/CD from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Implementing CI/CD

A data engineer wants to develop pipeline code in an isolated branch inside the Databricks workspace, commit changes, and open a pull request for review before merging to main — all using the workspace's built-in Git integration. Which feature supports this?

  1. AUse notebook revision history, which keeps a version of each notebook save and lets reviewers compare and approve the saved versions of a feature copy before its changes are merged into main.
  2. BUse DBFS versioning, which creates a separate branch for each notebook edit and exposes a pull-request workflow so the team can review the changes before they reach the main branch.
  3. CUse Unity Catalog table versioning, which tracks source-code branches alongside the underlying data and lets pipeline code changes be committed, reviewed and merged inside the workspace.
  4. DUse the cluster event log, which records the commits and merges made on each branch and supplies the branching, review and pull-request workflow the engineer needs inside the workspace.
  5. EUse Databricks Git folders (formerly Repos), which provide branch creation and switching, commit and push, and pull-request creation through the connected Git provider inside the workspace.
Answer & explanation

Correct answer: E

WHY E: Databricks Git folders integrate the workspace with a Git provider, enabling branch creation and switching, commit and push, and pull-request creation from within Databricks.

WHY NOT A: Notebook revision history is autosave versioning of a single notebook, not Git branches or pull requests; it has no review-and-merge workflow.

WHY NOT B: DBFS has no branching model and does not create a branch per edit or expose pull requests.

WHY NOT C: Unity Catalog versions data (Delta time travel), not source-code branches.

WHY NOT D: The cluster event log records compute events such as start, resize and termination, not code commits or merges.

Take the full DE Associate practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Engineer Associate practice test. Take it and get a section-by-section score.

Start the free test →