Question

Your SRE team supports a payments API with a 99.9% availability SLO. Historically the development team owned feature velocity while SRE owned reliability, and the two groups frequently clashed after the error budget was exhausted—developers wanted to keep shipping and SRE wanted a freeze. Leadership asks you to redesign the operating model so that both teams share responsibility and decisions become data-driven rather than political. Which change most directly establishes this shared-ownership model?

Accepted Answer

Establish a documented error budget policy, agreed upon by both development and SRE leadership in advance, that automatically dictates the actions (such as halting feature releases) taken when the budget is depleted.

Answer

Increase the availability SLO to 99.99% so there is more headroom, giving developers more room to ship features before the budget runs out.

Answer

Transfer full ownership of the service, including on-call and release decisions, to the SRE team so a single group makes all reliability calls.

Answer

Remove the SLO entirely and rely on the development team's judgment to decide when the service is reliable enough to keep releasing.