An organization needs to grant an external network security auditor read-only access to inspect Virtual Private Cloud (VPC) firewall rules and Compute Engine virtual machine instance configurations within a single Google Cloud project named `prod-network-sec`. The auditor must not be allowed to make structural changes, view sensitive data payloads, or automatically inherit access to other projects under the same organization node. Which of the following IAM role assignments satisfy these requirements while adhering to the principle of least privilege? (Select TWO choices.)
- Grant the Compute Viewer (`roles/compute.viewer`) role to the auditor at the `prod-network-sec` project level.Cevap
- Grant the Security Reviewer (`roles/iam.securityReviewer`) role to the auditor at the `prod-network-sec` project level.Cevap
- CGrant the Editor (`roles/editor`) role to the auditor at the `prod-network-sec` project level.
- DGrant the Compute Viewer (`roles/compute.viewer`) role to the auditor at the parent Organization resource level.
Cevap
The auditor should be granted the Compute Viewer (`roles/compute.viewer`) role and the Security Reviewer (`roles/iam.securityReviewer`) role, both bounded explicitly to the target `prod-network-sec` project level.
To satisfy the auditing requirements under the principle of least privilege, predefined roles specific to the required capabilities must be assigned at the narrowest relevant resource boundary. The Compute Viewer role provides read-only visibility into compute resources within the project, while the Security Reviewer role grants access to view security configurations such as firewall rules and IAM policies. Both bindings must be applied at the project level to prevent unintended inherited access across other projects.
Adım Adım Çözüm
Anahtar Kavram
Applying Least Privilege via Scoped Predefined IAM Roles