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 enterprise e-commerce platform running on Google Cloud consists of three distinct service tiers:
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?
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.
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.
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.
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.
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.
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.
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.
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.
Aligning SLOs with service criticality ensures that the business does not over-engineer low-impact systems while maintaining robust defenses for critical revenue streams.
StudyCerts
StudyCerts