Databricks Data Engineer Associate Question 80
Select 3Which limitations in Databricks Notebooks' version control functionality make Databricks Repos a better choice for managing collaborative workflows?
- A
Databricks Notebooks do not support integration with Git-based version control systems.
- B
Databricks Notebooks lack the ability to manage multiple files or directories as a single versioned entity.
- C
Databricks Notebooks do not provide built-in branching and merging capabilities for collaborative workflows.
- D
Databricks Notebooks cannot be exported or imported as files to and from external version control systems.
- E
Databricks Notebooks' version history is limited to changes made directly in the notebook interface.
Show answer and explanation
Correct answers: B, C, E
Explanation
Databricks Notebooks have limitations that make them less suitable for advanced version control workflows. They lack support for managing multiple files or directories, branching and merging capabilities, and a robust version history. These features are natively supported by Databricks Repos, which leverage Git for comprehensive version control and collaboration.
- A. Incorrect.
Incorrect: Databricks Notebooks can integrate with Git-based version control systems, allowing users to link and save changes directly to repositories.
- B. Correct.
Correct: Databricks Notebooks operate on a single-file basis and do not allow managing multiple files or directories as a cohesive versioned entity, unlike Repos.
- C. Correct.
Correct: Databricks Notebooks do not natively support branching and merging workflows, which are essential for collaborative development. Repos provide this capability through Git integration.
- D. Incorrect.
Incorrect: Databricks Notebooks can be exported or imported to and from external systems, making this functionality available.
- E. Correct.
Correct: The version history in Databricks Notebooks is limited to changes made within the notebook interface and lacks the detailed commit tracking available in Repos.