Answer-first summary for fast verification
Answer: Each developer creates a branch for their own work, commits their changes to their branch, and merges their code into the main branch daily.
Google recommends trunk-based development as a best practice for high software delivery rates. This approach involves developers working on short-lived branches and merging changes into the main branch frequently (often multiple times a day). Option C aligns with this practice by having developers create branches, commit changes to them, and merge into the main branch daily. This ensures continuous integration, reduces merge conflicts, and maintains code stability. Other options are less ideal: Option A risks late-stage integration issues, Option B uses infrequent merges, and Option D introduces delays via a change advisory board, which contradicts the principle of rapid, automated integration.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
As a developer in a large organization using Git for source control, what Google-recommended SCM process should your team adopt to optimize software delivery performance?
A
Each developer commits their code to the main branch before each product release, conducts testing, and rolls back if integration issues are detected.
B
Each group of developers copies the repository, commits their changes to their repository, and merges their code into the main repository before each product release.
C
Each developer creates a branch for their own work, commits their changes to their branch, and merges their code into the main branch daily.
D
Each group of developers creates a feature branch from the main branch for their work, commits their changes to their branch, and merges their code into the main branch after the change advisory board approves it.
No comments yet.