
Ultimate access to all questions.
A junior data engineer is working within a Databricks Repos notebook on a personal branch containing outdated logic. They need to review the latest code in the dev-2.3.9 branch; however, this branch is not appearing in the branch selection dropdown.
What is the correct approach to allow the developer to review the current logic in the dev-2.3.9 branch?
A
Merge the personal branch with dev-2.3.9 and create a pull request to synchronize with the remote repository.
B
Fetch the latest changes from the remote Git repository and then switch to the dev-2.3.9 branch once it appears.
C
Use the Databricks REST API to create a pull request and force the Repos environment to update to dev-2.3.9.
D
Check out the dev-2.3.9 branch using the Git CLI to automatically resolve any merge conflicts with the current branch.