Question

A payments team is defining an SLO for their checkout API using Cloud Monitoring service monitoring. Their stated reliability goal is that 99.5% of requests should complete in under 400 ms, measured over a rolling 28-day period. The team wants the SLO configuration to accurately reflect this goal so error budget calculations and burn-rate alerts behave as expected. Which SLO configuration correctly represents this objective?

Accepted Answer

A request-based, latency-threshold SLI with a 400 ms threshold, a 99.5% goal, and a rolling 28-day compliance period.

Answer

A windows-based availability SLI with a 99.5% goal and a calendar-month compliance period, using uptime checks as the signal.

Answer

A request-based availability SLI counting HTTP 2xx responses with a 99.5% goal and a rolling 7-day compliance period.

Answer

A windows-based latency SLI with a 400 ms threshold, a 99.5% goal, and a calendar 28-day compliance period.