Databricks Data Engineer Associate Question 78
Select 2Which of the following is a limitation of Databricks Notebooks' built-in version control functionality compared to Databricks Repos?
- A
Databricks Notebooks do not support integration with Git-based workflows.
- B
Databricks Notebooks lack the ability to handle collaborative branching and merging.
- C
Databricks Notebooks automatically track all changes with a detailed commit history.
- D
Databricks Notebooks cannot revert to a specific previous version.
- E
Databricks Notebooks do not allow users to synchronize changes with a remote repository.
Show answer and explanation
Correct answers: B, E
Explanation
Databricks Notebooks offer basic version control features such as revision history, but they lack advanced Git-based functionality like collaborative branching, merging, and remote repository synchronization. For these capabilities, Databricks Repos is required. Understanding these limitations is key to choosing the right tool for version control in Databricks.
- A. Incorrect.
Incorrect: While Notebooks do not natively integrate with Git-based workflows, users can utilize Databricks Repos for Git integration. This is a limitation of Notebooks but not exclusive to version control functionality.
- B. Correct.
Correct: Databricks Notebooks lack advanced Git-based version control features like collaborative branching and merging, which are supported by Databricks Repos.
- C. Incorrect.
Incorrect: Databricks Notebooks do track changes with a basic history of edits, but this is limited compared to Repos' Git-based commit tracking.
- D. Incorrect.
Incorrect: Databricks Notebooks allow users to revert to specific previous versions using the revision history feature.
- E. Correct.
Correct: Databricks Notebooks do not support synchronization with remote repositories, a feature provided by Databricks Repos.