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 is migrating its core transactional platform to Google Cloud. To meet aggressive release deadlines, the development team has increased deployment frequency, but consecutive unstable releases have caused major service disruptions and completely exhausted the service's monthly error budget.
The operations team wants to halt all cloud migrations and institute mandatory, multi-stakeholder manual change approval gates for every release, while the development team insists on maintaining release velocity.
Which approach aligns with Site Reliability Engineering (SRE) change management principles to resolve this conflict and balance innovation velocity with system stability?
A Change Advisory Board (CAB) is a traditional ITIL governance process where a committee of stakeholders reviews, evaluates, and manually approves proposed changes prior to deployment into production environments.
The organization were operating under rigid legacy compliance regulations requiring dual-custody human sign-offs on low-frequency, monolithic on-premises systems without CI/CD automation capabilities.
This approach removes repository branch protections, peer review mechanisms, and least-privilege IAM controls, allowing any individual developer to merge changes and execute emergency changes directly in production.
The project were an isolated, non-production sandbox environment with no live users, data, or operational reliability requirements.
A 100% availability SLO assumes that a system should never experience downtime or errors under any circumstances. Combining this with individual reprimands creates a blame-centric culture that punishes engineers for system failures.
There were safety-critical hard real-time systems where any failure results in loss of life, though even in those cases, blameless culture and systemic failure analysis remain industry standards.
In Site Reliability Engineering (SRE), the error budget represents the acceptable level of unreliability that a service can experience within a specific timeframe without violating its Service Level Objective (SLO). It acts as an objective, data-driven governance mechanism that balances product development velocity with infrastructure and service reliability.
When a service depletes its error budget, the pre-negotiated policy mandates an operational shift: instead of continuing rapid feature launches, the development team redirects engineering effort toward stabilizing the application. Conducting blameless post-mortems ensures that outages are treated as learning opportunities to uncover systemic weaknesses, process gaps, and missing automated guardrails rather than assigning individual fault.

This approach directly implements SRE best practices by using the error budget as an automated feedback loop. It guarantees that release velocity is constrained only when reliability falls below agreed thresholds, keeping the organizational transformation focused on automation and measurable quality.
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