Databricks Certified Data Engineer - Professional
Get started today
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 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?
Real Exam
Last updated: January 6, 2026 at 15:42A
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.
Comments
Loading comments...