Question

Your SRE team is preparing a new payments API for general availability. The product team has committed to an availability SLO of 99.9% measured over a rolling 28-day window. During load testing, the service handles 2,000 requests per second at target latency, but at 2,600 requests per second, the p99 latency doubles and error rates climb above the SLO threshold. Marketing projects a launch-day peak of 2,400 requests per second, with sustained growth afterward. As part of the service lifecycle and launch-readiness review, what should the team do BEFORE approving GA?

Accepted Answer

Provision and validate enough capacity headroom (with autoscaling and load-shedding safeguards) to serve well beyond the projected 2,400 RPS peak while meeting the SLO, then approve GA.

Answer

Lower the SLO to 99.5% so the projected launch traffic stays within the error budget, then approve GA immediately.

Answer

Approve GA as-is since the projected peak of 2,400 RPS is below the 2,600 RPS point where the SLO was breached in testing.

Answer

Delay defining any SLO until after launch so real production traffic can inform the availability target.