Databricks Data Engineer Associate Question 77
Select 3You are working on a large-scale data engineering project in Databricks and need to track changes to your codebase. While exploring version control options, you notice limitations in using Databricks Notebooks' native version control compared to using Repos. Which of the following limitations apply to Databricks Notebooks' version control when compared to Repos?
- A
Databricks Notebooks do not support branching or merging workflows natively.
- B
Databricks Notebooks cannot integrate with external Git providers like GitHub or Azure DevOps.
- C
Databricks Notebooks' version history is limited to the same workspace and cannot be shared across multiple workspaces.
- D
Databricks Notebooks allow collaborative editing but do not support detailed commit messages for version changes.
- E
Databricks Notebooks support granular file and folder-level version control similar to Repos.
Show answer and explanation
Correct answers: A, C, D
Explanation
Databricks Notebooks' version control is basic and workspace-specific, lacking advanced features like branching, merging, and detailed commit tracking. Repos, on the other hand, integrate deeply with external Git providers, enabling robust version control workflows suitable for collaborative data engineering projects.
- A. Correct.
Correct: Databricks Notebooks lack native support for branching and merging workflows, which are key features of version control systems like Git and Repos.
- B. Incorrect.
Incorrect: Databricks Notebooks can integrate with external Git providers, allowing users to sync their notebooks with repositories on GitHub, Azure DevOps, etc.
- C. Correct.
Correct: Version history in Databricks Notebooks is tied to the workspace and cannot be shared or exported across multiple workspaces, unlike Repos which leverage external Git systems.
- D. Correct.
Correct: While collaborative editing is supported, Databricks Notebooks do not allow users to attach detailed commit messages to changes, which limits their usefulness compared to Git-based commit tracking in Repos.
- E. Incorrect.
Incorrect: Databricks Notebooks do not support granular file or folder-level version control like Repos, which are designed to work with Git repositories for this functionality.