Databricks Certified Data Engineer - Professional
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
A junior developer is experiencing unexpected results in a Databricks Repos notebook. Upon investigation, they realize they are working on a personal branch with outdated code. They need to switch to the dev-2.3.9 branch to review the correct logic, but this branch is currently missing from the branch selection menu.
What is the most direct and lowest-risk way for the developer to access the code on the dev-2.3.9 branch?
A
Select the option to checkout the dev-2.3.9 branch via the Repos UI and use the 'auto-resolve conflicts' toggle to handle discrepancies with the current branch.
B
Initiate a pull request through the Repos interface and execute a Databricks REST API call to force the workspace branch to dev-2.3.9.
C
Use the 'Pull' button in the Repos Git dialog to fetch latest updates from the remote repository, then select dev-2.3.9 from the refreshed branch dropdown.
D
Merge all local modifications into the main branch in the remote repository and perform a full re-clone of the repository into the Databricks workspace.
E
Merge the current personal branch into the dev-2.3.9 branch using the Repos UI, then create a pull request to synchronize the changes with the remote server.