A global gaming company structures its Google Cloud resource hierarchy with an Organization node containing top-level folders named Game-Services and Corporate-IT. The infrastructure team needs to grant a group of site reliability engineers (SREs) full administrative access to Compute Engine resources across all current and future projects nested inside the Game-Services folder. The security team requires strict compliance with the principle of least privilege while minimizing management overhead. Which IAM assignment strategy should be implemented?
- Grant the Compute Admin role (roles/compute.admin) to the SRE group at the Game-Services folder level.Answer
- BGrant the Editor primitive role (roles/editor) to the SRE group at the Game-Services folder level.
- CGrant the Service Account Admin role (roles/iam.serviceAccountAdmin) to the SRE group at the Game-Services folder level.
- DGrant IAM permissions at the individual project level and configure VPC Service Controls to restrict Compute Engine management across folders.
Answer
Grant the Compute Admin role (roles/compute.admin) to the SRE group at the Game-Services folder level.
In Google Cloud IAM, policies applied at a folder node are inherited by all resource containers beneath it, including current and future projects. Assigning the predefined Compute Admin role (roles/compute.admin) at the Game-Services folder level satisfies least privilege for Compute Engine resources while eliminating the administrative burden of granting per-project permissions.
Step-by-Step Solution
Key Concept
Resource Hierarchy IAM Policy Inheritance and Predefined Roles
Estimated Time:1m 30s