Your organization structures its Google Cloud resources using a resource hierarchy where the Finance department operates within a dedicated folder containing several workload projects. A compliance auditor requires read-only permissions to inspect configuration settings across all current projects within the Finance folder, as well as any new projects created inside this folder in the future. Following Google Cloud recommended practices and the principle of least privilege, which action should you take?
- Grant the predefined Security Reviewer role (roles/iam.securityReviewer) on the Finance folder.Answer
- BGrant the primitive Owner role (roles/owner) on the Finance folder.
- CGrant the Security Reviewer role (roles/iam.securityReviewer) individually on each project currently inside the folder.
- DGrant the Billing Account Viewer role (roles/billing.viewer) on the Organization node.
Answer
Grant the predefined Security Reviewer role (roles/iam.securityReviewer) on the Finance folder.
In Google Cloud's resource hierarchy, IAM policies applied at a parent container (such as a folder) are automatically inherited by all child resources, including existing and future projects. Binding the predefined Security Reviewer role at the Finance folder level fulfills the auditing access requirement dynamically while strictly adhering to the principle of least privilege.
Step-by-Step Solution
Key Concept
Resource Hierarchy IAM Policy Inheritance and Predefined Roles