An enterprise e-commerce platform running on Google Cloud consists of three distinct service tiers: Tier 1 (Critical Revenue): Checkout and Payment Processing services where customer-facing downtime directly causes immediate financial loss and brand damage. Tier 2 (Core User Experience): Product Search and Catalog browsing services where brief degradation reduces user engagement but does not halt active checkouts. Tier 3 (Internal/Asynchronous): Recommendation Engine and Back-office Analytics batch processing where delays of several hours do not impact real-time customer transactions. The leadership team wants to establish an SRE cost-benefit framework to set Service Level Objectives (SLOs) that balance reliability investments against feature velocity and development costs. Which strategy should the organization implement to optimize reliability targets across these tiers?

Establish differentiated SLO targets by tier, allocating high-nines targets (such as 99.99%) and high engineering prevention budgets only to Tier 1, while assigning relaxed SLOs (such as 99.9% and 99.0%) with larger error budgets to Tiers 2 and 3 to maximize feature velocity.: ### What Tiered Reliability Modeling Is **Tiered reliability modeling** is an SRE framework that establishes distinct **Service Level Objectives (SLOs)** based on the business impact of unavailability for each service class. Rather than treating all components uniformly, the organization maps engineering and infrastructure investment directly to business risk. ### How It Meets Business and Technical Requirements * **Cost of Unavailability vs. Cost of Prevention:** In **Tier 1**, an outage causes immediate revenue loss and severe reputational damage. The **cost of unavailability** far exceeds the **cost of prevention**, justifying multi-region redundancy, automated failover, and strict change gating to achieve 99.99% availability. * **Balancing Feature Velocity with Reliability:** For **Tier 2** and **Tier 3**, the cost of unavailability is significantly lower because users can tolerate slight latency or delayed batch computation. Assigning relaxed SLOs (e.g., 99.9% or 99.0%) creates larger **error budgets**, giving product teams the freedom to iterate rapidly and take calculated deployment risks without wasting engineering capacity on unneeded reliability. * **Diminishing Returns on Extreme Nines:** Each incremental "nine" of availability (e.g., moving from 99.9% to 99.99% or 99.999%) increases capital and operational expenditures exponentially while yielding diminishing returns in end-user satisfaction. ### Key Advantages of This Framework * **Optimized Resource Allocation:** Directs premium SRE and engineering efforts toward high-impact, revenue-critical pipelines. * **Sustainable Innovation Pace:** Prevents non-critical services from blocking releases due to overly restrictive error budget policies. * **Data-Driven Investment Decisions:** Uses clear economic trade-offs to justify architectural enhancements and redundancy. ### Why This Is Optimal Aligning SLOs with service criticality ensures that the business does not over-engineer low-impact systems while maintaining robust defenses for critical revenue streams.

Sre Tiered Slo Cost Benefit Framework | Professional Cloud DevOps Engineer

Sre Tiered Slo Cost Benefit Framework

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 e-commerce platform running on Google Cloud consists of three distinct service tiers:

Tier 1 (Critical Revenue): Checkout and Payment Processing services where customer-facing downtime directly causes immediate financial loss and brand damage.
Tier 2 (Core User Experience): Product Search and Catalog browsing services where brief degradation reduces user engagement but does not halt active checkouts.
Tier 3 (Internal/Asynchronous): Recommendation Engine and Back-office Analytics batch processing where delays of several hours do not impact real-time customer transactions.

The leadership team wants to establish an SRE cost-benefit framework to set Service Level Objectives (SLOs) that balance reliability investments against feature velocity and development costs.

Which strategy should the organization implement to optimize reliability targets across these tiers?

Assign the highest availability SLO (99.99%) to Tier 3 batch systems because asynchronous workloads can be isolated, while assigning 99.0% to Tier 1 checkout services to accommodate rapid feature changes.

Define SLOs dynamically based on historical trailing uptime metrics for each service, lowering SLO targets whenever a deployment consumes the error budget to avoid freezing releases.

Establish differentiated SLO targets by tier, allocating high-nines targets (such as 99.99%) and high engineering prevention budgets only to Tier 1, while assigning relaxed SLOs (such as 99.9% and 99.0%) with larger error budgets to Tiers 2 and 3 to maximize feature velocity.

Standardize a uniform 99.999% availability SLO across all tiers, allocating an equal share of engineering capacity and multi-region infrastructure to every microservice to eliminate operational risk.

Professional Cloud DevOps Engineer

Sre Tiered Slo Cost Benefit Framework

Related questions