Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A financial enterprise uses a multi-tier Google Cloud resource hierarchy structured as follows:
example.com
Engineering
Backend-Services
payment-prod
payment-logsA security administrator reviews the following IAM allow policy bindings for the user auditor@example.com across this lineage:
roles/viewer granted on the Engineering folderroles/storage.objectViewer granted on the Backend-Services folderroles/storage.admin granted on the payment-prod projectTo prevent auditor@example.com from modifying objects in the payment-logs bucket, the administrator removes all bucket-level role bindings so that no direct allow policy is set on payment-logs.
What is the effective permission level of auditor@example.com on the payment-logs bucket, and why?
In Google Cloud, the resource hierarchy organizes resources into a parent-child structure consisting of the organization, folders, projects, and individual service resources. IAM allow policies are attached to these container nodes and are inherited down the tree. The union of all allow policies applied directly to a resource and its ancestors forms the effective allow policy.
payment-prod project), that role automatically propagates to all descendant resources within that container.roles/storage.admin is granted at the payment-prod project level, the user inherits complete control (storage.buckets.* and storage.objects.*) over every bucket in that project, including payment-logs.
Understanding that allow policies are strictly cumulative ensures cloud architects recognize that restricting access requires modifying the specific ancestor node where the role was granted, implementing IAM Deny policies, or using separate trust boundaries (projects/folders) to achieve least privilege.
roles/storage.objectViewer role granted on the Backend-Services folder overrides lower project-level policies.Assigning roles/storage.objectViewer on the Backend-Services folder grants read access to Cloud Storage objects across all child folders and projects within that specific folder subtree.
roles/storage.admin granted at the project level adds full management capabilities on top of the inherited roles/storage.objectViewer permissions.Google Cloud IAM allow policies followed an explicit nearest-ancestor override rule where lower or higher hierarchical assignments completely suppressed all other bindings, which is not how IAM operates.
roles/viewer access because the highest parent container in the hierarchy sets the maximum permissible access ceiling.Granting roles/viewer at the top-level Engineering folder allows the principal to view resource configurations across all projects and resources nested within that folder.
roles/storage.admin on payment-prod) expand the principal's total permissions for those downstream resources.Basic IAM allow policies on parent containers acted as restrictive permission boundaries or access scopes that capped child permissions.
Bucket-level IAM allow policies provide granular access control directly on a specific Cloud Storage bucket. They allow administrators to assign roles to users specifically for that individual bucket without granting access across the entire Google Cloud project.
roles/storage.admin as fully authoritative for all operations on buckets inside that project.Google Cloud resources operated in an isolated security silo requiring explicit localized authorization bindings on every discrete resource before ancestral policies were acknowledged.
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