Answer: Databricks Repos supports the use of multiple branches

## Explanation **Correct Answer: B** - Databricks Repos supports the use of multiple branches **Why this is correct:** 1. **Multiple Branch Support**: Databricks Repos integrates with Git repositories, which inherently support branching. This allows data engineers to: - Create feature branches for new development - Maintain stable main/master branches for production code - Create release branches for specific versions - Collaborate effectively using Git workflows 2. **Comparison with Built-in Notebooks Versioning**: - Built-in Databricks Notebooks versioning provides basic version history and the ability to revert to previous versions - However, it lacks Git integration and doesn't support branching workflows - Built-in versioning is more like a simple revision history system **Why other options are incorrect:** - **A**: Both Databricks Notebooks versioning and Databricks Repos automatically save development progress. This is not a distinguishing advantage. - **C**: Both systems allow users to revert to previous versions of a notebook. Built-in versioning provides this functionality through the notebook's revision history. - **D**: Commenting on specific changes is typically a feature of Git platforms (like GitHub, GitLab, Bitbucket) rather than Databricks Repos itself. Databricks Repos provides Git integration but doesn't inherently provide code review/commenting features within the Databricks interface. - **E**: Both Databricks Notebooks versioning and Databricks Repos are housed within the Databricks Lakehouse Platform, so this is not a distinguishing advantage. **Key Takeaway**: The primary advantage of Databricks Repos over built-in notebook versioning is its Git integration, which enables proper version control workflows including branching, merging, and collaboration through external Git repositories.

Author: Keng Suppaseth