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 organizes its Google Cloud resources under an Engineering parent folder, which contains two subfolders: Development and Production. A security auditor discovers that the group dev-team@example.com is currently bound to the Compute Instance Admin role (roles/compute.instanceAdmin) directly on the Engineering folder.
The security team must enforce the following access requirements:
Development folder.roles/compute.viewer) for Compute Engine instances within projects located in the Production folder.Which architectural change should the security team implement to satisfy these access requirements?
This approach attempts to remove role bindings from individual project allow policies under the Production folder while keeping the parent Engineering folder binding intact.
roles/compute.instanceAdmin on Engineering, every project in Production still resolves the effective permission set as Compute Instance Admin.The roles/compute.instanceAdmin role had originally been granted directly at each individual project level rather than inherited from a parent folder.
Scoped role assignment involves applying IAM allow policies at the most granular, appropriate container level within the resource hierarchy rather than at an overly broad parent node.
roles/compute.instanceAdmin directly on the Development folder ensures that all child projects and Compute Engine instances beneath it inherit instance administration permissions.roles/compute.viewer directly on the Production folder provides developer access to view infrastructure without inheriting administrative permissions from a parent folder.Engineering folder) prevents unwanted permissions from propagating down into production workloads.In Google Cloud IAM, allow policies are strictly additive and inherited downwards through the resource hierarchy. A child resource's effective policy is the union of all allow policies attached to the resource and its ancestors. Because an allow policy at a child level cannot revoke, restrict, or override an inherited allow permission from a higher level, removing the high-privilege grant from the parent node and scoping distinct roles at the child folder level is the standard and correct approach.
This configuration attempts to override inherited administrative privileges by setting resource-level IAM allow policies directly on individual Compute Engine virtual machine instances.
roles/compute.viewer directly on the VM cannot subtract the administrative permissions granted higher up at the Engineering folder.A user needed read-only access to a single specific VM instance while having no inherited permissions across the parent project or folder.
This configuration leaves the high-privilege roles/compute.instanceAdmin role on the ancestor Engineering folder while adding an additional role binding for roles/compute.viewer on the descendant Production folder.
roles/compute.viewer at the Production folder adds read permissions to the user's token, but it does nothing to remove or restrict the roles/compute.instanceAdmin permissions inherited from Engineering.This approach would only be meaningful if the group initially had no access at the folder level and required viewer access across all sub-resources in Production.
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