Answer: Databricks Repos supports the use of multiple branches

## Explanation Databricks Repos provides Git integration that supports multiple branches, which is a key advantage over the built-in Databricks Notebooks versioning. Let's analyze each option: **A. Databricks Repos automatically saves development progress** - This is also true for built-in Notebooks versioning, which automatically saves versions as you work. **B. Databricks Repos supports the use of multiple branches** - ✅ **CORRECT**. This is a key advantage of Databricks Repos over built-in Notebooks versioning. Repos provides full Git integration including branch management, while built-in versioning doesn't support branching. **C. Databricks Repos allows users to revert to previous versions of a notebook** - Both Repos and built-in versioning allow reverting to previous versions, so this is not an advantage unique to Repos. **D. Databricks Repos provides the ability to comment on specific changes** - This is a Git feature available through Repos, but built-in versioning also has commenting capabilities. **E. Databricks Repos is wholly housed within the Databricks Lakehouse Platform** - Both are housed within Databricks, so this is not a differentiating advantage. **Key Differences:** - **Databricks Notebooks Versioning**: Built-in automatic versioning within Databricks Workspace - **Databricks Repos**: Git integration with external repositories (GitHub, GitLab, Bitbucket, Azure DevOps), supporting full Git workflows including branching, pull requests, and collaboration features. The ability to use multiple branches enables better collaboration, feature development, and code management workflows that are standard in modern software development practices.

Author: Keng Suppaseth