Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An organization hosts a customer-facing payment processing service on Google Cloud using a regional multi-zone deployment (Compute Engine Regional Managed Instance Groups across three zones and Cloud SQL configured for High Availability), targeting an availability Service Level Objective (SLO) of 99.99% (approximately 52 minutes of allowed downtime per year).
Executive leadership requests upgrading the availability target to 99.999% ("five nines", allowing roughly 5 minutes of downtime per year) by migrating to an active-active multi-region deployment across two Google Cloud regions using Cloud Spanner and global load balancing.
As the Site Reliability Engineer (SRE) evaluating this proposal, which assessment accurately reflects the technical, financial, and operational trade-offs of this incremental reliability improvement?
Migrating to an active-active multi-region deployment reduces overall total cost of ownership (TCO) and operational overhead because Cloud Spanner and global external HTTP/S load balancers natively automate all failure domains without requiring custom engineering or testing.
Achieving 99.999% availability guarantees that the application tier reaches 100% uptime with zero single points of failure, completely eliminating the need for error budgets and change freezes.
The transition requires zero architectural changes to data consistency models because regional Cloud SQL configurations automatically scale across multiple regions with sub-millisecond synchronous cross-region write performance.
Achieving the marginal reduction of ~47 minutes of annual downtime exponentially increases infrastructure cost (duplicate compute capacity, multi-region database pricing, cross-region network traffic) and introduces substantial operational complexity, which can divert specialized engineering resources away from product feature velocity.
Migrating to an active-active multi-region deployment reduces overall total cost of ownership (TCO) and operational overhead because Cloud Spanner and global external HTTP/S load balancers natively automate all failure domains without requiring custom engineering or testing.
Achieving 99.999% availability guarantees that the application tier reaches 100% uptime with zero single points of failure, completely eliminating the need for error budgets and change freezes.
The transition requires zero architectural changes to data consistency models because regional Cloud SQL configurations automatically scale across multiple regions with sub-millisecond synchronous cross-region write performance.
Achieving the marginal reduction of ~47 minutes of annual downtime exponentially increases infrastructure cost (duplicate compute capacity, multi-region database pricing, cross-region network traffic) and introduces substantial operational complexity, which can divert specialized engineering resources away from product feature velocity.
In Site Reliability Engineering (SRE), every additional "nine" of availability incurs exponentially increasing financial, architectural, and operational costs while delivering diminishing marginal returns in downtime reduction. Moving from 99.99% availability (~52.6 minutes of downtime per year) to 99.999% availability (~5.26 minutes of downtime per year) eliminates only about 47 minutes of annual downtime, but requires a fundamental shift in architecture and team allocation.
This option provides an accurate and holistic SRE evaluation of the non-linear relationship between cost, complexity, and availability gains. For many business workloads, the immense cost of "five nines" cannot be justified unless the financial or regulatory impact of ~47 minutes of annual downtime exceeds the multi-million-dollar cost of multi-region operational overhead.