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.
An enterprise organization contains a folder named Core-Infrastructure, which contains a child project named network-prod. A cloud engineer who is a member of the Google Group ops-engineers@example.com is granted the Project Deleter role (roles/resourcemanager.projectDeleter) directly on the network-prod project. To prevent accidental resource deletion, a security administrator attaches an IAM deny policy to the Core-Infrastructure folder that specifies principalSet://goog/group/ops-engineers@example.com in deniedPrincipals and cloudresourcemanager.googleapis.com/projects.delete in deniedPermissions.
What is the result when this engineer attempts to delete the network-prod project, and how does IAM evaluate the request?
Rule merging is a behavior found in certain Organization Policy Service legacy list constraints, where allowed and denied value lists from ancestor and descendant nodes are combined according to hierarchy evaluation rules. However, IAM policies do not use net-positive rule merging.
deniedPrincipals and the action matches deniedPermissions, the request is rejected immediately without calculating net permissions.exceptionPrincipals or exceptionPermissions fields inside the deny rule itself.IAM evaluated permissions by tallying positive allow bindings against negative deny bindings and resolving conflicts in favor of the most granular positive assignment.
IAM allow policies define role bindings that grant permissions to identities on resources. In Google Cloud, allow policies are strictly additive across the resource hierarchy, meaning permissions granted at an organization, folder, or project level accumulate.
Google Cloud IAM operated on an allow-override model where explicit resource-level allow grants took precedence over ancestor deny policies, which is contrary to IAM's security architecture.
The Organization Policy Service provides centralized control over resource configurations (what configurations or behaviors are allowed on resources), such as disabling service account key creation or restricting resource locations. It functions separately from IAM, which governs identity authorization (who can perform what actions).
cloudresourcemanager.googleapis.com/projects.delete, the API call is denied at the authorization layer without consulting the Organization Policy Service.IAM lacked native deny capabilities and relied entirely on Organization Policy constraints (such as custom constraints or managed boolean constraints) to prevent administrative deletion actions.
IAM deny policies provide declarative security guardrails that prevent principals from using specific permissions on Google Cloud resources and all of their descendant resources. Unlike IAM allow policies—which are additive and grant access—deny policies explicitly block access across the resource hierarchy.
When a principal attempts to perform an operation on a Google Cloud resource, IAM performs a structured evaluation across all relevant policy types:
In this scenario, because the Core-Infrastructure folder contains an active deny policy blocking cloudresourcemanager.googleapis.com/projects.delete for ops-engineers@example.com, the deny rule is inherited down to network-prod and halts the evaluation at stage 2.
roles/resourcemanager.projectDeleter or roles/owner at the project level cannot grant access blocked by a parent deny rule.inheritFromParent: false—IAM deny policies enforce immutable denial across all descendants.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