A cloud-native organization is not meeting their service level objective (SLO) but has not exhausted their error budget. What should the organization prioritize?

The correct answer is C. Stability to avoid prolonged user downtime. An SLO defines the target reliability level for a service. An error budget is the allowable amount of unreliability within a given period. If the organization is not meeting its SLO, that means reliability has already fallen below the acceptable threshold - even if the error budg

Site Reliability Engineering (SRE) Principles

Question

Options

AInnovation to improve user experience
BHardware reliability to improve availability
CStability to avoid prolonged user downtime
DSpeed to release new features

How the community answered

(57 responses)

A
11% (6)
B
2% (1)
C
84% (48)
D
4% (2)

Explanation

An SLO defines the target reliability level for a service. An error budget is the allowable amount of unreliability within a given period. If the organization is not meeting its SLO, that means reliability has already fallen below the acceptable threshold - even if the error budget hasn't been fully exhausted, the service is underperforming its reliability target. In this situation, the priority must be stability and fixing reliability issues to bring the service back within SLO. Focusing on new features or innovation when SLOs are being missed would further risk the service's reliability. The error budget remaining doesn't justify releasing new features when reliability targets are already being violated.

Topics

#SRE#SLO#Error Budget#Operational Priority

Community Discussion

No community discussion yet for this question.

Full CLOUD-DIGITAL-LEADER Practice