PROFESSIONAL-CLOUD-DEVELOPER · Question #287
Your company's security team uses Identity and Access Management (IAM) to track which users have access to which resources. You need to create a version control system that can integrate with your…
The correct answer is A. Create a Cloud Source Repositories repository, and use trunk-based development. The two requirements are: (1) native IAM integration for the security team, and (2) fast release cycles with frequent merges to minimize conflicts. Cloud Source Repositories (CSR) is a Google-managed Git service that integrates natively and seamlessly with Google Cloud IAM…
Question
Your company's security team uses Identity and Access Management (IAM) to track which users have access to which resources. You need to create a version control system that can integrate with your security team's processes. You want your solution to support fast release cycles and frequent merges to your main branch to minimize merge conflicts. What should you do?
Options
- ACreate a Cloud Source Repositories repository, and use trunk-based development.
- BCreate a Cloud Source Repositories repository, and use feature-based development.
- CCreate a GitHub repository, mirror it to a Cloud Source Repositories repository, and use trunk-
- DCreate a GitHub repository, mirror it to a Cloud Source Repositories repository, and use feature-
How the community answered
(48 responses)- A83% (40)
- B10% (5)
- C2% (1)
- D4% (2)
Explanation
The two requirements are: (1) native IAM integration for the security team, and (2) fast release cycles with frequent merges to minimize conflicts. Cloud Source Repositories (CSR) is a Google-managed Git service that integrates natively and seamlessly with Google Cloud IAM - access control is managed through the same IAM roles and policies the security team already uses, with no additional identity federation. Trunk-based development (committing directly or via short-lived branches to the main/trunk branch) directly supports fast releases and minimizes merge conflicts by keeping divergence small. Options C and D (GitHub mirrored to CSR) add unnecessary complexity and a dependency on a third-party platform. Option B (feature-based development) uses long-lived feature branches that diverge significantly, causing the merge conflicts the question explicitly wants to avoid.
Topics
Community Discussion
No community discussion yet for this question.