A developer has successfully configured Databricks Repos and cloned a remote Git repository. However, they lack permissions to commit directly to the `main` branch, which is currently the only branch visible in the environment. Which strategy should the developer use to share their code updates without risking an overwrite of their colleagues' work?

Real Exam

Last updated: January 6, 2026 at 15:42

Use Repos to fetch all modifications and share the git diff log with the team for manual review.

Utilize Repos to pull changes from the remote Git repository, then commit and push modifications to a branch that appeared during the fetch process.

Create a new branch within Databricks Repos, commit the local modifications, and push the new branch to the remote Git repository.

Initiate a fork of the remote repository directly from the Databricks Repos interface, execute the changes, and submit a pull request.

Merge all local discrepancies into the existing branch and then initiate a pull request to integrate changes into the remote repository.

Databricks Certified Data Engineer - Professional