Databricks Certified Data Engineer - Professional
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
A junior developer reports their notebook code is yielding incorrect results in the development environment. A screenshot shows they're using a notebook versioned in Databricks Repos but working on a personal branch with outdated logic. The required branch dev-2.3.9 does not appear in the branch dropdown menu.
What steps should the developer take to access and review the latest logic for this notebook?
A
Use Repos to make a pull request use the Databricks REST API to update the current branch to dev-2.3.9
B
Use Repos to pull changes from the remote Git repository and select the dev-2.3.9 branch.
C
Use Repos to checkout the dev-2.3.9 branch and auto-resolve conflicts with the current branch
D
Merge all changes back to the main branch in the remote Git repository and clone the repo again
E
Use Repos to merge the current branch and the dev-2.3.9 branch, then make a pull request to sync with the remote repository