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 establishing a standardized self-service provisioning and access management workflow for engineering teams in Google Cloud. The cloud architecture team must implement an access lifecycle model that meets the following security and governance requirements:
roles/editor upon creation.Which combination of IAM and governance controls should you implement?
Granting standing primitive roles (roles/owner) provides full administrative and destructive control over Google Cloud project resources. Scheduling nightly script-based teardowns attempts to clean up stale permissions by resetting the IAM policy file.
You were provisioning disposable, isolated sandbox environments that are completely destroyed and purged at the end of every business day.
Direct IAM assignments grant permissions directly to specific user email identities (user:developer@example.com). IAM Conditions allow administrators to define conditional expressions—such as request.time < timestamp('...')—to enforce time-limited access on individual policy bindings.
resourcemanager.organizationAdmin or roles/resourcemanager.projectIamAdmin to continuously modify project policy bindings for every request.roles/editor, violating least-privilege requirements during project provisioning.A single individual needed an emergency, one-off temporary bypass directly on a standalone resource where centralized access group management was unavailable.
Groups for Business (collaboration groups) are designed for unstructured communication, such as shared email lists and document collaboration. They generally allow open group creation by standard domain users and have loose membership controls.
The objective was to create an open mailing list or shared discussion board for developer collaboration rather than governing sensitive cloud infrastructure access.
constraints/iam.automaticIamGrantsForDefaultServiceAccounts organization policy constraint.Workload-specific access groups and Just-In-Time (JIT) group management tools provide a scalable, self-service mechanism for governing permissions across Google Cloud resources. Instead of binding IAM roles directly to individual users, roles are assigned to dedicated access groups representing specific job functions. A self-service tool (such as JIT Groups) evaluates access requests, enforces justification and approval workflows, and automatically expires user memberships when the approved duration concludes.

iam.automaticIamGrantsForDefaultServiceAccounts organization policy constraint disables the automatic assignment of roles/editor when new services or projects are provisioned.Combining JIT-managed access groups with organization policy constraints establishes a secure, repeatable self-service model. It enforces least-privilege access during runtime and guarantees baseline guardrails are inherited by every newly provisioned project.
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