A company organizes its Google Cloud resources into dedicated folders per department. The security team needs to grant a developer group read-only access to object content in all Cloud Storage buckets across all projects contained within the 'Data Analytics' folder. The solution must follow Google recommended best practices for least privilege and operational simplicity. Which IAM role assignment strategy should be implemented?
- Grant the predefined Storage Object Viewer role (roles/storage.objectViewer) to the group at the 'Data Analytics' folder level.Cevap
- BGrant the primitive Editor role (roles/editor) to the group at the 'Data Analytics' folder level.
- CGrant the Service Account User role (roles/iam.serviceAccountUser) to the group at the Organization root level.
- DRely solely on VPC Service Controls perimeters around the projects without binding any IAM roles at the folder or project level.
Cevap
Granting the predefined Storage Object Viewer role at the folder level leverages IAM resource hierarchy inheritance while enforcing the principle of least privilege.
In Google Cloud IAM, permissions defined on parent resources (such as Folders) are inherited downstream by all child resources (such as Projects and Cloud Storage buckets). Granting the predefined Storage Object Viewer role at the target folder level ensures that users receive the exact read permissions required for all present and future projects under that folder without granting unnecessary permissions.
Adım Adım Çözüm
Anahtar Kavram
Resource hierarchy inheritance and fine-grained predefined IAM roles