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: Routine operational changes to infrastructure must follow a version-controlled GitOps pipeline, with regular users restricted from directly creating or updating production resources. Site Reliability Engineers (SREs) and operators need visibility to monitor application health across project folders without having permissions to modify the underlying infrastructure. Emergency break-glass access must be established with 2 to 5 dedicated accounts configured with hardware FIDO security keys in a separate Organizational Unit (OU), ensuring any emergency intervention leaves an auditable trail in Cloud Audit Logs. Which governance and change management strategy should the enterprise implement?

Grant predefined view-only roles to monitoring personnel, restrict resource modification to CI/CD service accounts, and establish redundant break-glass users protected with FIDO security keys in a dedicated Organizational Unit.: ### What the solution is 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. ### How it meets the requirements - **Separation of duties & GitOps enforcement:** By granting operational teams and SREs view-only roles (such as `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. - **Auditable change tracking:** Automated pipeline deployments ensure all changes are tracked in version control, while Cloud Audit Logs automatically capture all API operations and administrative activity for compliance audits. - **Emergency access governance:** Creating between 2 and 5 emergency access users in a separate **Organizational Unit (OU)** ensures redundancy without single points of failure. Enforcing **FIDO security keys** and avoiding automated credential rotation maintains strict physical and cryptographic security controls for high-privilege emergency accounts. ### Key advantages - **Eliminates configuration drift:** Prevents manual out-of-band updates by disallowing direct human write access to production. - **High resilience:** Multiple emergency accounts protected by hardware keys guarantee access during catastrophic identity provider or pipeline outages. - **Full auditability:** Clean distinction between automated CI/CD service account changes and emergency human interventions in **Cloud Audit Logs**. ### Why this is optimal This approach aligns with Google Cloud architecture best practices for continuous access, strict change control, and regulatory compliance.

StudyCerts

Governance Separation Of Duties Emergency Access | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Governance Separation Of Duties Emergency Access

Section: Change management

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

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:

Routine operational changes to infrastructure must follow a version-controlled GitOps pipeline, with regular users restricted from directly creating or updating production resources.
Site Reliability Engineers (SREs) and operators need visibility to monitor application health across project folders without having permissions to modify the underlying infrastructure.
Emergency break-glass access must be established with 2 to 5 dedicated accounts configured with hardware FIDO security keys in a separate Organizational Unit (OU), ensuring any emergency intervention leaves an auditable trail in Cloud Audit Logs.

Which governance and change management strategy should the enterprise implement?

Provision a single emergency super-admin user enrolled in SMS-based multi-factor authentication, and grant all SREs the App Management Viewer role with full Editor permissions inherited from the organization root.

Assign project-level Owner roles to operational teams, use Cloud Audit Logs to detect manual changes after they occur, and configure an automated Cloud Function to rotate break-glass super-admin passwords every 24 hours.

Grant predefined view-only roles to monitoring personnel, restrict resource modification to CI/CD service accounts, and establish redundant break-glass users protected with FIDO security keys in a dedicated Organizational Unit.

Assign the Cloud Hub Operator role to all personnel, disable Cloud Identity two-step verification for emergency users to accelerate incident response, and store break-glass credentials in a shared software password manager.

Professional Cloud Architect

Governance Separation Of Duties Emergency Access

Related questions