Practice SLO implementation vocabulary: availability targets, error budgets, burn rates, budget exhaustion, and error budget alerting strategies.
0 / 12 completed
1 / 12
'We set a 99.9% ___ SLO.' Which noun describes the type of SLO?
A 99.9% availability SLO (Service Level Objective) means the service must be up and serving successfully for at least 99.9% of the time in a given window — about 43 minutes of allowed downtime per month.
2 / 12
'The error budget is 43 ___ per month.' Which unit of time fits a 99.9% SLO?
A 99.9% SLO allows 0.1% error — which equals approximately 43.2 minutes per 30-day month. The error budget is the amount of acceptable downtime or errors before the SLO is breached.
3 / 12
'We're burning 3× the error budget ___.' Which noun follows 'rate' in this context?
'Error budget burn rate' measures how fast the error budget is being consumed relative to the allowed rate. A 3× burn rate means the budget will be exhausted 3 times faster than planned.
4 / 12
'The SLO dashboard shows we have 12 ___ remaining.' Which unit fits error budget context?
Error budget remaining is typically expressed in time (minutes remaining in the budget window) or as a percentage. '12 minutes remaining' means the service can afford only 12 more minutes of downtime this month.
5 / 12
What is 'error budget alerting'?
Error budget alerting fires proactively based on burn rate — e.g., alert if you'll exhaust the budget in less than 2 days at current burn rate. This gives teams time to act before an SLO breach.
6 / 12
Alice from QA just commented on your PR: 'This change seems to be impacting latency. We're seeing a spike in response times during peak hours and it's exceeding our SLO for the API endpoint. Can you investigate?' Which of the following best describes the type of SLO being referenced here?
This question tests understanding of the core concept of an SLO. A latency SLO specifically focuses on the *time* it takes for a system to respond. Availability, throughput, and error rate SLOS address different aspects of service performance; the context provided clearly points towards response time.
7 / 12
Ben sent a Slack message: 'Hey team, we're currently burning through our error budget at a rate of 1.5x. We need to reduce this quickly!' What unit of time does the phrase '1.5x' most accurately represent within the context of an error budget?
The phrase '1.5x' directly indicates a rate of consumption. In the context of an error budget, this typically refers to the *hourly* or *time-based* rate at which errors are occurring. Burning through the budget is measured over time (e.g., per hour).
8 / 12
Sarah from Engineering is reviewing your PR and comments: 'The SLO for successful transactions is currently 99.9%. I'm seeing a drop to 99.8% over the last hour. What metric are we primarily tracking here?',
The question focuses on a percentage representing success, directly aligning with an error rate SLO. Availability considers uptime; latency measures response time; and throughput refers to the volume of requests processed – none of these are best represented by a percentage of successful operations. Therefore, 'Error Rate' is the most accurate term.
9 / 12
David, during a standup meeting, says: 'We're aiming for an error budget of 10% per month to cover unexpected issues. What does he mean by 'error budget' in this context?'.
An 'error budget' is a pre-allocated buffer within an SLO. It represents the acceptable deviation from the target – in this case, the maximum number of errors (bugs) that can occur before impacting service quality. The other options relate to different aspects of software development or incident management, but not the specific concept of an error budget as part of an SLO.
10 / 12
Maria sends a Slack message: 'The API is currently exceeding its SLO by 2.5x. We need to investigate immediately!' What does '2.5x' signify in this context?
When an SLO is exceeded by '2.5x', it means the API's actual performance (likely requests per second or throughput) is 2.5 times greater than the target defined within its SLO. This indicates a significant strain on resources and requires immediate attention to prevent further degradation of service. The other options represent different metrics, but not the amplification factor related to SLO targets.
11 / 12
John, in a code review comment, asks: 'How are we monitoring the impact of this change on our latency SLO?'. What is the primary method for tracking and reporting on latency SLOs?
Latency SLOs require continuous monitoring of response times. Automated synthetic transaction tests are specifically designed for this purpose – they mimic real user interactions and consistently measure latency under various load conditions. While server logs and manual testing can provide insights, automated tests offer the most reliable and scalable way to track and report on latency against a defined SLO.
12 / 12
Emily states: 'We've configured alerts for when our error rate exceeds 5% during peak hours. What is the purpose of these alerts?'.
Error rate alerting serves as a critical safety mechanism for SLOs. When an alert triggers – meaning the error rate surpasses the defined threshold (5% in this case) – it immediately notifies relevant stakeholders to investigate and take corrective action before service degradation occurs. The alerts don't directly scale servers or block users; they simply signal a problem requiring attention.
What will I practise in "SLO Implementation Vocabulary"?
This module focuses on Observability Engineering — real workplace phrasing you'll use on the job. It contains 12 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 12 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Observability Engineering exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around observability engineering — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Observability Engineering exercises?
See the Observability Engineering hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.