Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
A DevOps team is managing access across a multi-tier Google Cloud resource hierarchy. A developer reports that they are unable to delete objects from a specific Cloud Storage bucket in a production project, despite having the Storage Object Admin (roles/storage.objectAdmin) role directly granted to their identity on that bucket.
During your investigation of the resource hierarchy, you identify the following IAM configurations:
storage.objects.delete to all members of the developer group.roles/storage.objectViewer) role.roles/storage.objectAdmin) role.How does Google Cloud IAM evaluate these cumulative policies to determine the developer's effective permissions on the bucket?
Resource-level allow policies attach directly to specific supported resources (such as Cloud Storage buckets, BigQuery datasets, or Pub/Sub topics) to grant fine-grained permissions to principals on that individual resource.
In Google Cloud IAM, allow policies do not "override" ancestor policies based on resource proximity:
Google Cloud used a cascading override model where leaf-node access control lists (ACLs) superseded root policies, but Google Cloud IAM enforces centralized governance where parent deny guardrails cannot be overridden by child resources.
Folder-level allow policies grant IAM roles across all projects, subfolders, and individual cloud resources nested inside that folder. In this scenario, granting Storage Object Viewer (roles/storage.objectViewer) gives read access to objects across the entire folder hierarchy.
Allow policies in Google Cloud are strictly additive and cannot narrow or restrict permissions:
IAM allow policies behaved like AWS Permissions Boundaries or restrictive subnet masks where parent bindings limit the maximum allowable privilege of child resources. In GCP IAM, restricting permissions across child resources requires IAM deny policies or Principal Access Boundary (PAB) policies.
In Google Cloud Identity and Access Management (IAM), access evaluation follows a strict hierarchical evaluation order where IAM deny policies always take precedence over IAM allow policies, regardless of where the policies are attached in the resource hierarchy.
When the developer attempts to execute an action that requires storage.objects.delete on the Cloud Storage bucket, IAM resolves the request using the following evaluation sequence:
storage.objects.delete to the principal's group, the denial is absolute.roles/storage.objectAdmin) role—which contains the storage.objects.delete permission—this grant cannot supersede the ancestor deny rule.This evaluation model ensures that central governance and compliance guardrails set by organization security administrators cannot be inadvertently bypassed or overridden by project owners or resource-level administrators. Tools like Policy Troubleshooter and gcloud beta projects get-ancestors-iam-policy --include-deny can be used to quickly inspect these interacting layers.
Project-level IAM bindings assign roles across all resources located within a specific project. When a project contains no specific bindings for a user, that user simply receives no additional permissions from the project container itself.
Google Cloud IAM does not require an explicit allow grant at intermediate hierarchy levels for child resource bindings to work:
roles/viewer or roles/browser at the project level to access a resource if they interact directly with that resource via API or direct URI.Google Cloud enforced a mandatory hierarchy traversal model requiring explicit pass-through permissions at every intermediate node (Organization -> Folder -> Project -> Resource) before resource-level bindings could be evaluated.
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