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 designing a formal change management and governance framework for its Google Cloud production environment. The cloud architecture team must enforce separation of duties, ensure infrastructure modifications are fully audited, and prevent unauthorized manual drift while supporting rapid incident response.
The design must meet these key requirements:
Which governance and change management strategy should the enterprise implement?
This approach grants baseline operational viewing roles to staff but severely compromises the security of emergency administrative accounts by disabling multi-factor authentication and utilizing centralized software-based password storage.
The organization had no external network exposure, zero compliance requirements, and prioritized instantaneous, unauthenticated recovery over credential security.
This option provisions a single emergency user relying on SMS multi-factor authentication and grants broad roles/editor rights to SREs across the entire organization hierarchy.
The environment was an unmanaged personal sandbox where only one administrator existed and full organization-wide editing was needed for testing.
This approach relies on granting broad, highly privileged administrative roles (roles/owner) directly to operational engineers while relying entirely on post-hoc detective controls (auditing) and automated scripts to manage break-glass passwords.
The organization operated a non-production development sandbox where rapid, unrestricted prototyping by all developers was prioritized over compliance, separation of duties, and change control.
This strategy establishes a robust change governance framework by combining least-privilege IAM roles, GitOps automation, and emergency break-glass procedures. It enforces separation of duties between viewing operational status and deploying production changes.
roles/apphub.appManagementViewer or roles/cloudhub.operator), personnel can monitor applications without possessing direct write permissions. All production modifications must flow through version-controlled CI/CD pipelines executed by dedicated service accounts.
This approach aligns with Google Cloud architecture best practices for continuous access, strict change control, and regulatory compliance.
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