Topic 1 Question 80
2 つ選択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?
Add more serving capacity to all of your application's zones.
Have more frequent or potentially risky application releases.
Tighten the SLO match the application's observed reliability.
Implement and measure additional Service Level Indicators (SLIs) fro the application.
Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.
ユーザの投票
コメント(17)
I would go for B+D: -A: no, there's no reason to add capacity if we are barely scratching error budget; -B: everything seems fine, so it's ok to dare with more innovative/risky releases; -C: no, stakeholders said SLO is ok; -D: adding additional SLIs (and so SLOs) might be a way to reflect observer reliability more closely; -E: put the servers down for no reason is a no-no.
👍 18Trony2021/11/03- 正解だと思う選択肢: DE
I vote for D+E if you read "The Global Chubby Planned Outage" https://sre.google/sre-book/service-level-objectives/
👍 10Sekierer2022/01/20 - 正解だと思う選択肢: BE
B - You can increase the frequency of your releases and take higher risks as you have never exceeded your error budget. E - Planned downtime to use some of your error budget will help to make sure end users don’t get use a higher availability of your service.
👍 6PhilipKoku2022/02/13
シャッフルモード