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?
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.