PROFESSIONAL-CLOUD-DEVOPS-ENGINEER practice question 4 of 25

[Applying Site Reliability Engineering (SRE) principles to a service] You support a user-facing web application. When analyzing the application’s…

Full set: 205 questions
[Applying Site Reliability Engineering (SRE) principles to a service] 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.)
Answer options
A: Add more serving capacity to all of your application’s zones.
B: Have more frequent or potentially risky application releases. Correct answer
C: Tighten the SLO match the application’s observed reliability. Correct answer
D: Implement and measure additional Service Level Indicators (SLIs) fro the application.
E: Announce planned downtime to consume more error budget, and ensure that users are not depending on a tighter SLO.
Correct Answer:
B. Have more frequent or potentially risky application releases.; C. Tighten the SLO match the application’s observed reliability.
Explanation

When a service consistently and significantly overachieves its SLO, it indicates a mismatch between the business goal (the SLO) and reality. This can lead to users developing a dependency on a higher level of reliability than is guaranteed. SRE principles suggest two main paths:
1. Tighten the SLO (C) to more accurately reflect the service's actual performance. This makes the reliability promise to users more honest.
2. Use the excess error budget to increase development velocity (B). This means shipping features more frequently or taking on more calculated risks, knowing there is a large buffer to absorb potential failures without breaching the SLO. Both actions help balance reliability with business needs.

Why Incorrect

A. Adding more capacity is unnecessary and costly, as the application is already exceeding its reliability targets.
D. The prompt states the SLO was reviewed and confirmed as appropriate, implying the existing SLIs are sufficient. Adding more SLIs doesn't address the over-performance issue.
E. While planned downtime can be used to manage user expectations, it doesn't inherently increase velocity or make the SLO more accurate, which are the primary goals.

References

1. Beyer

B.

Jones

C.

Petoff

J.

& Murphy

N. R. (2016). Site Reliability Engineering: How Google Runs Production Systems. O'Reilly Media. Chapter 4

"Service Level Objectives

" Section "Motivation for Error Budgets

" p. 43: "An error budget is a clear

objective metric that determines how unreliable the service is allowed to be... This metric makes it possible to have a productive discussion... about the risks of a new release."

2. Jones

C.

Beyer

B.

et al. (2018). The Site Reliability Workbook. O'Reilly Media. Chapter 5

"Implementing SLOs

" Section "Refining SLOs

" p. 70: "If you are consistently not spending your error budget... you should consider tightening the SLO... Alternatively

you can use your error budget to take more risks and increase your release velocity."

Scroll to Top