A new release of a recommendation service makes responses about 40% slower. Latency still sits inside the 300 ms SLO, and no alerts have fired yet. What is the most appropriate next step for the team?
Show answer and explanation
Answer: C
An SLO is a floor for acceptable behavior, not a license to degrade. A release that makes a service noticeably slower may still be inside the target while users suffer and the trend heads toward a breach. The team should measure real user impact, look at the trajectory, and weigh whether to roll back or fix forward. Ignoring the change because budget remains misreads the purpose of the target, and loosening the SLO to fit the release is the wrong fix. A full shutdown would be disproportionate.
Why the other options are wrong
- A. Having budget remaining does not make a visible slowdown acceptable. Leaving a degrading release in place without assessment lets the trend reach a breach unnoticed.
- B. Changing the target after the fact hides the regression and removes the signal the SLO exists to provide. It excuses the change rather than assessing it.
- D. Taking the whole service offline is a drastic response to a regression that is still within target. It causes far more user harm than the slowdown itself.