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.
Your company is designing the access control architecture for its production Google Cloud environment. To comply with regulatory standards and enforce separation of duties, the organization must establish strict administrative isolation.
The security policy mandates the following requirements:
Which IAM role configuration should you implement to satisfy these requirements?
roles/editor) role combined with the Security Reviewer (roles/iam.securityReviewer) role to the security administratorsThe Editor (roles/editor) role provides broad permissions to create, modify, and delete most cloud resources, but does not grant permissions to modify IAM allow policies. The Security Reviewer (roles/iam.securityReviewer) role provides read-only access to review IAM policies, organization policies, and asset configurations across the organization or project.
A developer or operations engineer needed permission to deploy application components while a compliance officer only needed to inspect and review security configurations.
Security Reviewer is intended for audit and security analysis teams (grp-gcp-security-reviewer), not for administrators responsible for active policy enforcement and role assignments.
roles/owner) role to a dedicated Google Group containing the security administratorsThe Owner (roles/owner) role is a legacy basic role that provides full administrative and operational control over all Google Cloud resources in a project, including managing IAM policies, creating/deleting resources, and modifying billing configurations.
The organization required universal, emergency break-glass administrative capabilities where an identity must hold unrestricted control over all project resources and policies.
Google Cloud security best practices advise replacing primitive basic roles (Owner, Editor, Viewer) with fine-grained predefined roles.
roles/resourcemanager.organizationAdmin) role to individual administrator user accountsThe Organization Administrator (roles/resourcemanager.organizationAdmin) role grants full administrative authority over the entire Google Cloud organization resource, including resource hierarchy reorganization, organization policy enforcement, and root-level IAM delegation.
A centralized cloud foundation team needed root-level authority to structure folders, apply organization policies, and establish initial resource hierarchy boundaries across the entire enterprise.
To ensure scalability and security hygiene, always bind predefined roles to Google Groups federated from your identity provider rather than directly attaching privileges to individual user accounts.
roles/resourcemanager.projectIamAdmin) role to a dedicated Google Group containing the security administratorsThe Project IAM Admin (roles/resourcemanager.projectIamAdmin) role is a predefined Identity and Access Management role in Google Cloud. It provides permissions to administer allow policies and manage IAM access controls at the project level without granting direct access to resource workloads or data planes.
roles/resourcemanager.projectIamAdmin allows security administrators to manage role bindings, update allow policies, and control access delegation without inheriting operational privileges to interact with workload data or modify runtime resources.
resourcemanager.projects.getIamPolicy and resourcemanager.projects.setIamPolicy specifically.Using roles/resourcemanager.projectIamAdmin bound to a group isolates administrative policy functions from data plane access. It avoids the excessive operational power of basic roles like Owner while satisfying strict separation of duties.
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