Google Professional Cloud Developer
Get started today
Ultimate access to all questions.
To integrate with your security team's IAM-based access tracking while supporting rapid release cycles and frequent merges to minimize conflicts, what version control approach should you implement?
To integrate with your security team's IAM-based access tracking while supporting rapid release cycles and frequent merges to minimize conflicts, what version control approach should you implement?
Explanation:
The question emphasizes integrating with IAM for access tracking and minimizing merge conflicts through frequent merges. Trunk-based development aligns with frequent merges to the main branch, reducing conflicts. Cloud Source Repositories (CSR) directly integrates with Google Cloud IAM, enabling the security team to manage access via IAM policies. While GitHub mirroring (options C/D) could work, the primary repository in CSR (option A) ensures native IAM integration without relying on external GitHub permissions. Feature-based development (options B/D) involves longer-lived branches, increasing merge risks. Thus, the correct choice is A.