Exam Certified Data Engineer Professional topic 1 question 91 discussion

Answer E. Creating a new branch within the repository is the most effective and recommended approach for developers who lack write access to the main branch in Databricks Repos. While forking is a valid strategy in some situations, it's generally less common and potentially more complex within the context of Databricks Repos, especially when the primary goal is to contribute to the existing shared repository.

I changed my mind i think is E

Explanation: The developer does not have privileges to make changes to the main branch of the remote repository, and it's the only branch visible in their workspace. To share their code updates without risking overwriting their teammates' work, the best approach is to: Create a personal copy (fork) of the remote repository. This forked repository will be under the developer's own account or workspace, allowing full control over it. Make Changes in the Fork: Commit all code updates to the forked repository. Since the developer has full privileges on their fork, they can create branches, commit changes, and manage the repository as needed. Option E: Creating a new branch and pushing changes to the remote repository requires write access to the repository, which the developer does not have. By forking the repository, the developer avoids any permission issues and ensures that their work does not interfere with the main codebase until it is reviewed and approved by the team.

E is the regular collaboration approach. B makes a fork so breaks away from the collaborating teamates. There's no way they can make a pull request on the source repository after making change to a fork.

Databricks Repos itself does not currently support creating forks directly within the platform. However, you can achieve a similar workflow using the following steps: Use the git clone command in a terminal or IDE to create a local copy of the remote repository. This effectively creates a local fork. Make your changes in the local copy. Use git push to push your changes to a new remote repository you create on a Git hosting service like GitHub. Create a pull request from your new remote repository to the original repository on Databricks Repos. This approach allows you to make changes to your own copy of the code, collaborate with others through code reviews, and propose your changes for integration into the main branch without directly modifying it

This is a common workflow in collaborative development environments. The developer can create a new branch in their local repository, make changes, and then push the branch to the remote repository. This way, they can share their updates without modifying the main branch directly. After pushing the changes, they can create a pull request on the remote repository, allowing their teammates to review the changes before merging them into the main branch. This process ensures that the main branch remains stable and that all changes are reviewed and approved before they’re incorporated. It also prevents any accidental overwrites of teammates’ work.

Databricks Repos cannot be used to fork a repository

E is correct

E is correct if you create a fork you create another repository so not B

B is correct

B is correct

Isn't this B?