You support a user-facing web application. When analyzing the application’s error budget over the previous six months, you notice that the application has never consumed more than 5% of its error budget in any given time window. You hold a Service Level Objective (SLO) review with business stakeholders and confirm that the SLO is set appropriately. You want your application’s SLO to more closely reflect its observed reliability. What steps can you take to further that goal while balancing velocity, reliability, and business needs? (Choose two.)
A. Add more serving capacity to all of your application’s zones.
B. Have more frequent or potentially risky application releases.
C. Tighten the SLO to match the application’s observed reliability.
D. Implement and measure additional Service Level Indicators (SLIs) for the application. Most Voted
E. Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO. Most Voted
Disclaimer
This is a practice question. There is no guarantee of coming this question in the certification exam.
Answer
D, E
Explanation
DE – You want your application’s SLO to more closely reflect its observed reliability.
https://sre.google/sre-book/service-level-objectives/
Refer “The Global Chubby Planned Outage”.
A. Add more serving capacity to all of your application’s zones.
(There’s no reason to add capacity if we are barely scratching error budget.)
B. Have more frequent or potentially risky application releases.
(Sounds good, but introducing new changes could add errors, that do not match the current objectives “You want your application’s SLO to more closely reflect its observed reliability.”)
C. Tighten the SLO to match the application’s observed reliability.
(SLO is set appropriately they say.)
D. Implement and measure additional Service Level Indicators (SLIs) for the application.
E. Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.