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.
An enterprise organization is structuring its Google Cloud resource hierarchy to maintain a strict separation of duties across departments. The company must satisfy the following security and governance requirements:
Which resource hierarchy and access management architecture should the organization implement?
This configuration pools all company projects into a single shared container, grants the Security team full Organization Administrator privileges, and relies on developer impersonation of project-level Owner service accounts.
Owner role gives developers full unrestricted power within projects, bypassing least privilege and enabling them to alter security and IAM bindings locally.Organization Administrator rights without specific audit/review guardrails exposes the organization to administrative risk.Owner permissions to those service accounts destroys fine-grained role separation.The organization were running a monolithic multitenant application where a single administrative group managed all operations and programmatic workloads without departmental boundaries.
This approach grants broad, primitive IAM roles (roles/owner and roles/editor) directly at the top-level Organization resource, relying on standard downstream inheritance to distribute permissions across all existing and future child resources.
Owner role gives them full administrative control over workload deployments, deletions, and IAM configurations, directly violating the requirement that security oversight remain independent and read-only regarding workload operations.Editor role at the Organization node allows any developer to view, modify, or delete resources in all projects and across all other departmental boundaries.The organization were running a single-user sandbox environment with no security boundaries, compliance requirements, or departmental divisions.
This architecture establishes a structured Google Cloud resource hierarchy utilizing top-level folders mapped by department, combined with distinct Identity and Access Management (IAM) role assignments at precise hierarchy tiers to maintain separation of duties.
roles/orgpolicy.policyAdmin and roles/iam.securityReviewer (or roles/viewer) at the Organization node allows central administration of guardrails and read-only visibility across every child folder and project without granting workload deployment or data modification permissions.roles/compute.instanceAdmin.v1 or roles/editor) scoped strictly to their respective departmental folders ensures development teams cannot affect neighboring business units.This model follows the principle of least privilege and strict segregation of duties. High-level access is limited to auditing and policy enforcement, while resource-creation privileges remain confined to leaf or departmental scopes.
This option eliminates intermediate folder structures by placing all projects directly under the organization root, assigning project-level Editor roles to security personnel and organization-level Viewer roles to developers.
Editor role on projects allows them to alter application resources, violating the mandate that security oversight must not have workload deployment/edit permissions.Viewer at the organization node prevents them from provisioning or managing their departmental compute infrastructure unless overridden with additive permissions on each project.Developers required global cross-departmental read access, while security engineers were tasked with day-to-day infrastructure maintenance without any requirement for folder-level policy inheritance.
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