Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A security engineer is evaluating IAM access across an organization's resource hierarchy structured as follows:
Finance-Deptfin-analytics-prod (child of Finance-Dept)fin-audit-logs (located inside fin-analytics-prod)The following IAM allow policies are currently configured:
Finance-Dept Folder level, the principal auditor@example.com is granted the Storage Admin (roles/storage.admin) role.fin-analytics-prod Project level, auditor@example.com is granted the Storage Object Viewer (roles/storage.objectViewer) role.fin-audit-logs Bucket level, a local administrator attempts to restrict access by granting auditor@example.com only the Storage Object Creator (roles/storage.objectCreator) role.What is the effective permission state of auditor@example.com on the fin-audit-logs bucket, and why?
Identity and Access Management (IAM) in Google Cloud uses a hierarchical container model (Organization → Folders → Projects → Resources). In this hierarchy, child resources automatically inherit the IAM allow policies configured on all of their parent ancestors. The union of all allow policies applied directly to a resource and inherited from its parent hierarchy forms the effective allow policy.
Finance-Dept): The user auditor@example.com was granted roles/storage.admin, which contains full management and object manipulation permissions across all Cloud Storage buckets within that folder.fin-analytics-prod): Granting roles/storage.objectViewer adds read permissions, but does not diminish or revoke the folder-level administrative role.fin-audit-logs): Granting roles/storage.objectCreator adds object creation permissions directly on the bucket.fin-audit-logs.Recognizing that allow policies propagate additively is critical for designing least-privilege security boundaries. When restrictions are needed, administrators must either move the resource outside the parent folder, remove the high-level role grant, or implement explicit IAM Deny policies.
Resource-level allow policies are IAM policies attached directly to individual resources (such as Cloud Storage buckets, BigQuery datasets, or Pub/Sub topics) to manage granular access permissions.
roles/storage.objectCreator on fin-audit-logs merely adds the storage.objects.create permission to the existing inherited permissions; it cannot suppress the inherited roles/storage.admin role.Google Cloud IAM operated on an override-based precedence hierarchy similar to some filesystem file permission models where explicit object-level permissions completely supersede parent folder permissions.
To actually restrict permissions on a child resource without altering parent allow policies, security engineers must configure IAM Deny policies, which explicitly prevent principals from executing specified permissions regardless of allow bindings.
Folder-level IAM policies are designed to manage access across multiple projects and descendant folders grouped under a shared organizational unit.
roles/storage.admin role granted on Finance-Dept fully reaches all storage buckets within fin-analytics-prod.Folders acted merely as administrative groupings for organizational metadata without active IAM policy inheritance, requiring explicit role grants inside each individual project.
Because folder policies propagate across all child projects, administrators must adhere to the principle of least privilege when assigning roles at the folder level, reserving broad roles for organization-wide or department-wide service management.
When a principal is assigned multiple IAM roles at different levels of the hierarchy, Google Cloud IAM reconciles them through an evaluation process that unions all granted permissions.
Google Cloud IAM enforced strict mutual exclusivity rules requiring uniform role definitions across every tier of the resource hierarchy.
While multiple role grants do not cause technical conflicts, redundant or mismatched grants make auditing difficult and can lead to accidental privilege creep, making regular effective permission analysis essential.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated