Your organization uses SRE principles to manage a Linux-based public REST API. Management wants a service-level objective (SLO) that can be monitored automatically. Which of the following statements BEST represents a well-formed SLO for request latency?
The API must be highly available at all times and respond quickly.
If monthly uptime falls below 99.95%, the provider will credit the customer 10% of the bill.
Return latency measurements are exported every 60 seconds to Prometheus.
99.95% of HTTP requests must return a 2xx or 3xx status code within 300 ms over any rolling 30-day window.
A valid SLO must combine a measurable service-level indicator, a quantitative target, and an explicit time window. "99.95% of HTTP requests must return a 2xx or 3xx status code within 300 ms over any rolling 30-day window" satisfies all three elements, making it monitorable and actionable. The vague statement about the API being "highly available" lacks numbers and a period, so it cannot be tested. The statement that introduces bill credits defines contractual penalties, so it is an SLA, not an SLO. Exporting metrics every 60 seconds is an implementation detail of monitoring and does not express a reliability target.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the difference between an SLO and an SLA?
Open an interactive chat with Bash
What are common service-level indicators (SLIs) used in SRE?
Open an interactive chat with Bash
Why is it important to have a rolling time window in SLOs?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Troubleshooting
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access