Topic 1 Question 353
You are a developer at a large organization. Your team uses Git for source code management (SCM). You want to ensure that your team follows Google-recommended best practices to manage code to drive higher rates of software delivery. Which SCM process should your team use?
Each developer commits their code to the main branch before each product release, conducts testing, and rolls back if integration issues are detected.
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.
Each developer creates a branch for their own work, commits their changes to their branch, and merges their code into the main branch daily.
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 before each major release.
ユーザの投票
コメント(2)
- 正解だと思う選択肢: C
Agree with C
👍 109bd94b2025/02/20 - 正解だと思う選択肢: C
Google-recommended best practices for source code management emphasize trunk-based development. In this approach, each developer works on a feature branch for their own work and merges their changes into the main branch frequently (ideally daily). This frequent integration minimizes merge conflicts, improves visibility of changes, and promotes continuous integration and delivery. • Option A: Committing directly to the main branch only before releases increases the risk of integration issues and delays feedback. • Option B: Copying the repository and merging before each product release introduces unnecessary complexity and delays integration. • Option D: Merging feature branches only before major releases can lead to large, disruptive changes and integration problems.
Thus, Option C aligns best with the practice of frequent integration and continuous delivery, driving higher rates of software delivery and reducing integration risks.
👍 1Sandesh242025/03/01
シャッフルモード