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 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?
Inverted SLO prioritization allocates higher availability targets and stricter error budget constraints to back-office or non-critical background services while loosening requirements on customer-facing revenue flows.
Tier 3 was an auditable real-time fraud prevention engine whose failure halted all commerce, while Tier 1 was a static promotional landing page.
A metric-following dynamic SLO adjusts its compliance targets downward retroactively to match observed service failures or outages during a given monitoring window.
An organization was conducting an initial short-term exploratory phase to discover baseline performance before formalizing initial SLO targets.
A uniform 99.999% availability strategy attempts to hold every microservice in the enterprise to less than six minutes of cumulative downtime per year, regardless of the service's actual business impact.
All microservices handled life-critical, regulatory, or high-frequency financial trading workflows where any split-second outage carried catastrophic consequences across the entire system.
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.
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