Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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?
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.
This option asserts that achieving 99.999% availability eliminates downtime entirely, obviating the need for SRE core practices like error budgets and code freezes.
Theoretical systems could achieve zero-defect execution and perfect fault tolerance, which is impossible in real-world distributed cloud computing.
This option claims that Cloud SQL can provide sub-millisecond synchronous replication across multiple regions without architectural changes or latency penalties.
Cloud SQL supported zero-latency global synchronous writes across multi-continental distances, which violates physical networking constraints and product specifications.
This option incorrectly assumes that adopting managed multi-region services like Cloud Spanner and Google Cloud Global External Application Load Balancers eliminates operational overhead and reduces infrastructure spending.
A team were comparing moving from an unmanaged on-premises data center to a single-region managed service where infrastructure maintenance toil is reduced without changing the geographic scope.
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 Validated