Answer-first summary for fast verification
Answer: Use Databricks Repos to fetch updates from the remote Git repository, then select and switch to the `dev-2.3.9` branch from the dropdown.
In **Databricks Repos**, the branch selection dropdown only displays branches that have been fetched to the local environment. If a specific remote branch (such as `dev-2.3.9`) is missing from the list, the user must first perform a 'Fetch' or 'Pull' operation. This updates the local view of all remote branches available from the Git provider. Once the list is refreshed, the developer can select the desired branch and switch to it. **Why other options are incorrect:** * **A and B:** You cannot merge with or check out a branch that the local environment hasn't 'seen' yet; furthermore, Databricks does not perform automatic conflict resolution during a checkout. * **D:** Pull requests and REST API updates affect the remote repository or Git provider state but do not automatically refresh the local branch metadata in the Databricks UI.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A junior developer is experiencing incorrect results in their development environment notebook. Upon inspection, it is discovered that they are working on a personal branch with outdated logic within Databricks Repos. They want to switch to the dev-2.3.9 branch to review the updated logic, but that branch is not visible in the branch selection dropdown.
Which action should the developer take to access and review the dev-2.3.9 branch?
A
Use Databricks Repos to check out the dev-2.3.9 branch and allow the system to automatically resolve any merge conflicts with the current branch.
B
Merge the current personal branch with dev-2.3.9 and create a pull request to synchronize with the remote repository.
C
Use Databricks Repos to fetch updates from the remote Git repository, then select and switch to the dev-2.3.9 branch from the dropdown.
D
Create a pull request via the Databricks REST API to force the current branch to update to the state of dev-2.3.9.
No comments yet.