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 is structuring access for its engineering teams across distinct application environments organized into Development, Testing, and Production folders in Google Cloud. The organization has the following access and operational requirements:
Development folder.Production folder must be restricted strictly to squad leads.Which Cloud Identity group hierarchy and IAM binding design should the security engineer implement?
This approach grants a broad, highly privileged primitive/predefined role (such as Project Editor or Owner) to all staff at the Organization root resource, and then relies on IAM Deny policies placed on lower-level folders (such as Production) to selectively block specific squads or non-lead users.
roles/editor at the organization root grants sweeping access across the entire resource hierarchy by default, creating immense security risk.Project Editor instead of granular predefined or custom roles grants unnecessary permissions, such as modifying shared infrastructure and service configurations.The requirement specifically called for establishing organization-wide security guardrails to prevent specific high-risk actions (such as disabling Cloud Audit Logs or deleting KMS keys) across all users, regardless of their positive IAM role grants.
A nested group hierarchy in Cloud Identity (or Google Workspace) is an identity architecture where specialized sub-groups (child/leaf groups) are added as members of higher-level parent groups. In Google Cloud IAM, permissions bound to a parent group are transitively inherited by all members of any nested child groups. This design separates identity lifecycle management (membership updates in Cloud Identity) from access policy management (IAM role bindings attached to folders and projects).
squad-alpha-devs@example.com and squad-beta-devs@example.com) are directly assigned administrative IAM roles on their respective squad projects within the Development folder.all-engineers@example.com) is granted read-only roles (e.g., roles/viewer, roles/logging.viewer) at the Development and Testing folder levels. Nesting squad-alpha-devs@ and squad-beta-devs@ into all-engineers@ ensures every engineer automatically inherits non-production read access without duplicate role assignments.squad-leads@example.com group is created and bound to elevated roles at the Production folder level. Squad engineers are not added to this group, preventing unintended privilege escalation.This approach aligns with Google Cloud enterprise landing zone best practices by combining hierarchical resource governance (environment folders) with role-based identity abstractions (nested groups). It eliminates manual user-level IAM bindings and minimizes administrative overhead across multi-environment deployments.
A flat group design avoids nesting and instead creates separate, independent groups for each combination of environment, squad, and permission level (such as dev-squad-alpha@, test-all-devs@, and prod-leads@), with individual user accounts explicitly added to every relevant group.
The organization had strict governance rules prohibiting nested group memberships in their identity provider or if the directory service lacked support for group-in-group relationships.
Direct user IAM assignment involves adding individual user email addresses (user:developer@example.com) directly into IAM policy bindings on Google Cloud organizations, folders, or projects, rather than managing permissions through Cloud Identity groups.
The organization had a very small team (1-2 developers), operated a single sandbox project, and had no requirement for centralized identity lifecycle management or environment segregation.
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