At any given time, Universal Containers has 10 Apex developers building new functionality and fixing bugs. Which branching strategy should an Architect recommend that mitigates the risk of developers overwriting others changes?
A.
Have all developers build new functionality in new branches, but fix bugs in the HEAD
B.
Have all developers work in the same branch, continuously testing for regressions
C.
Have developers work in separate branches and merge their changes in a common branch for testing
D.
Don't use source control. Rely on Salesforce's built-in conflict detection mechanism
This is the correct answer because having developers work in separate branches and merge their changes in a common branch for testing can reduce the risk of overwriting others’ changes and ensure code quality and consistency. Having all developers work in the same branch or in the HEAD may cause conflicts and errors. Not using source control is not a good practice and may result in data loss and lack of version control.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit