A cloud administrator needs to configure access for two team members working in a Google Cloud project. An compliance auditor requires read-only access to view IAM policy bindings across all resources in the project. Additionally, a security engineer needs to create and manage custom IAM roles within the project. Following Google's recommended practices for least privilege, which TWO IAM roles should the administrator grant? (Select TWO.)
- Grant the Security Reviewer role (roles/iam.securityReviewer) to the compliance auditor.Answer
- Grant the Role Administrator role (roles/iam.roleAdmin) to the security engineer.Answer
- CGrant the Editor primitive role (roles/editor) to both users at the project level to ensure full administrative visibility.
- DRevoke IAM permissions at the parent folder level to prevent inherited permissions from overriding project-level IAM roles.
Answer
The administrator should grant the Security Reviewer role (roles/iam.securityReviewer) to the compliance auditor and the Role Administrator role (roles/iam.roleAdmin) to the security engineer.
The Security Reviewer role provides read access to security and IAM configurations without permission to modify resources, fulfilling the auditor's requirement under least privilege. The Role Administrator role allows creating, editing, and deleting custom roles, satisfying the security engineer's duty without granting excess access to project workloads or data.
Step-by-Step Solution
Key Concept
Applying least privilege using predefined IAM roles for security auditing and custom role administration