5 exercises — Practice the vocabulary for SLO negotiations: discussing targets with product teams, explaining "tighter SLO means more investment," baseline and trade-off language.
0 / 30 completed
1 / 30
An SRE is in a meeting with a product team that wants to set an availability SLO of 99.99% for a new internal tool. The SRE responds: "Our current baseline is 99.92%. Moving to 99.99% is a significant reliability investment — let me explain what that means for the team." What does "current baseline" mean in this context?
"Current baseline" in SLO negotiations means the historically measured reliability of the service — the starting point from which any proposed SLO must be evaluated.
Why baseline matters in the negotiation:
• If the baseline is 99.92% and the product team wants 99.99%, they are asking the SRE team to improve reliability by 87.5% — a major engineering investment
• If the baseline is already 99.97%, moving to 99.99% may be achievable with targeted improvements
Standard SRE approach to SLO negotiation:
1. Present the baseline: "Our measured availability over the last 90 days is 99.92%"
2. Show the gap: "Your proposed SLO is 99.99% — that is a 7× reduction in allowed error rate"
3. Quantify the investment: "Achieving 99.99% requires redundant infrastructure, zero-downtime deployments, and 24/7 on-call — here is the engineering effort estimate"
Key vocabulary:
• current baseline — the historically measured reliability of the service, used as the starting point for SLO negotiation
• SLO gap — the difference between the proposed SLO and the current baseline
• reliability investment — engineering effort, infrastructure cost, and operational overhead required to meet a given SLO
• achievable SLO — a target the service can sustainably meet given current architecture and team capacity
2 / 30
During an SLO negotiation, an SRE says to a product manager: "A tighter SLO means more reliability investment — if we commit to 99.99%, we need to fund the redundancy work and increase on-call coverage." The PM replies: "We just want better reliability — why does it cost more?" Which response correctly explains the relationship?
The "each nine costs 10× more" heuristic captures why high availability is expensive: each additional nine means 10× less allowed downtime, requiring fundamentally more robust architecture.
To achieve 4.32 minutes/month of allowed downtime, the system needs:
• Multi-region redundancy (single region maintenance alone exceeds 4 minutes)
• Zero-downtime deployments (blue-green or canary)
• Automated failover with sub-minute RTO
• 24/7 on-call with strict response time SLAs
• Extensive chaos engineering and failure testing
The SRE's role in the negotiation is to make this explicit: "Here is what 99.99% requires — is the product value worth that investment?"
Key vocabulary:
• tighter SLO — a higher reliability target that reduces allowed downtime
• each nine of availability — an order-of-magnitude improvement in reliability (e.g., 99.9% to 99.99%)
• RTO (Recovery Time Objective) — the maximum acceptable time to restore service after an incident
• multi-region redundancy — running services in multiple data centres to survive single-region failures
3 / 30
In an SLO discussion, a product team says: "We need five-nines availability." The SRE asks: "What is the actual user impact if we miss by one nine — 99.999% vs. 99.99%?" The product team says they don't know. How should the SRE use this to guide the negotiation?
When a product team cannot articulate the user impact of a proposed SLO, the SRE's role is to ground the conversation in concrete user experience — not to accept or reject the target without evidence.
The user-impact anchoring technique:
1. Convert the SLO gap to real downtime: "99.999% vs. 99.99% = 26 seconds vs. 4.3 minutes per month"
2. Ask about user behaviour: "Do users abandon after 30 seconds? Is this a transactional service where every second of downtime is a lost sale?"
3. Present the cost of the tighter SLO: "Five-nines requires X months of engineering work — is that justified by the user impact?"
This is sometimes called the "SLO value conversation" — aligning the reliability target with actual business value rather than aspirational numbers. "Five-nines" is often used as shorthand for "very reliable" without precise understanding of what it means operationally.
Key vocabulary:
• five-nines — 99.999% availability; allows 26 seconds of downtime per month
• user impact — how a reliability degradation affects user behaviour or experience
• SLO value conversation — aligning the reliability target with business value, not technical aspiration
• SLO anchoring — grounding target proposals in measurable user experience data
4 / 30
After three months of discussions, an SRE and a product team reach an agreement. The SRE documents it as: "Agreed SLO: 99.9% availability over a rolling 30-day window. To be reviewed quarterly. If the service consistently achieves 99.95%+ for two consecutive quarters, the team will consider tightening to 99.95%." What principle does the review clause represent?
Iterative SLO refinement is the recommended approach: start with a conservative, achievable target and tighten it as the service proves reliable, rather than committing to an aspirational SLO before the infrastructure can support it.
The phased approach to SLO setting:
1. Baseline phase: set the SLO at or slightly below historical performance (no new investment required)
2. Evidence phase: run for 2-3 quarters, measure actual SLI vs. target
3. Refinement phase: if performance consistently exceeds the SLO, consider tightening; if consistently near the edge, improve infrastructure first
The benefit for negotiations: product teams get a commitment (99.9%) without the SRE team over-promising (99.99%). The quarterly review creates a structured path to higher reliability rather than a one-time negotiation that may not reflect what is achievable.
Key vocabulary:
• iterative SLO refinement — gradually tightening an SLO as the service demonstrates sustainable reliability
• conservative SLO — a target set below current performance to ensure it is achievable without heroic effort
• quarterly SLO review — a structured meeting to evaluate whether the SLO should be adjusted based on evidence
• tightening the SLO — raising the reliability target after evidence that the service can sustain higher performance
5 / 30
In a difficult SLO negotiation, a product team insists on 99.99% availability. The SRE responds: "We can commit to 99.99% if we deprioritise the reliability improvements for the payments service. Tighter SLO here means less budget for reliability elsewhere." What negotiation concept is the SRE introducing?
Reliability investment is a finite resource: committing to a tighter SLO for one service necessarily trades off engineering capacity from other areas — this is a core SRE negotiation principle that product teams must understand.
The trade-off framing is not a negotiation tactic — it reflects reality:
• Achieving 99.99% for one service may require dedicated on-call, redundant infrastructure, and continuous chaos testing
• Those resources come from the same engineering budget as reliability improvements for other services
• A portfolio of four services at 99.9% may be more valuable than one at 99.99% and three at 99%
How to present this effectively in a negotiation:
1. Map the engineering cost: "99.99% requires approximately 6 months of platform engineering work"
2. Name the trade-off explicitly: "That is the same capacity as the payments reliability project currently planned for Q3"
3. Ask the product team to make an informed choice: "Given this trade-off, do you still want to prioritise 99.99% here?"
Key vocabulary:
• reliability as finite resource — engineering capacity, infrastructure cost, and on-call bandwidth are limited
• SLO trade-off — committing to a tighter SLO for one service at the cost of reliability investment elsewhere
• reliability portfolio — the set of services and their SLOs, viewed as a portfolio of investments
• capacity allocation — how engineering time and infrastructure budget are distributed across reliability commitments
6 / 30
// Code Review Comment
"This endpoint currently has a 99.95% availability SLA. The team is pushing for 99.99%. Can we discuss the impact of this change on our monitoring and alerting strategy?"
What does 'availability SLA' refer to in this code review comment?
'Availability SLA' (Service Level Agreement) specifically defines the target percentage of uptime for a service. In this context, it's measuring how often the endpoint is functioning correctly – not simply if it's running. Options A, C, and D are related to infrastructure or cost but don't represent the core meaning of an SLA.
7 / 30
// Slack Message from SRE
SRE: "Hey @product_manager, just wanted to flag that a 99.99% availability SLO for this API would require significant architectural changes and increased operational overhead. It's a substantial investment."
The SRE's message focuses on 'substantial investment,' indicating that achieving 99.99% availability would demand considerable resources – primarily related to architecture and operations. Options A and C are incorrect; the SRE isn't immediately proposing or requesting a project. Option D is irrelevant to the core message.
8 / 30
{
"status": "error",
"code": 503,
"message": "Service Unavailable - Target availability of 99.99% was not met for the past hour."
}
What does the message in this API response primarily indicate?
The message 'Service Unavailable – Target availability of 99.99% was not met…' directly correlates to a violation of the service's SLO. When an SLO isn't achieved, services often temporarily become unavailable as a protective measure. Options A and D are incorrect, and option C addresses network issues.
9 / 30
'Implemented enhanced error handling and retry logic for the order processing service. This change is expected to improve availability to 99.95% over a rolling 30-day window.'
What does 'rolling 30-day window' signify in this PR description?
'Rolling' in this context means that the availability calculation isn't based on a single snapshot in time. Instead, it continuously updates its measurement using data from the preceding 30-day period – ensuring a more accurate reflection of recent performance. Options A and C are misinterpretations; option D is related to code review timing.
10 / 30
"We're currently focused on stabilizing the payment processing service after a recent spike in error rates. We've implemented some initial mitigation strategies, but we're still investigating the root cause and haven't yet achieved our 99.9% availability target."
The SRE's update clearly states that they haven't achieved their target availability – indicating an issue. It highlights their focus on investigation and mitigation. Options A and B are incorrect; option D is a request for resources, not a status report.
11 / 30
// Code Review Comment
"This endpoint currently has a 99.95% availability SLA. The team is pushing for 99.99%. Can we discuss the impact of this change on our monitoring and alerting strategy?"
What does 'availability SLA' refer to in this code review comment?
'Availability SLA' (Service Level Agreement) specifically defines the target percentage of uptime for a service. In this context, it's measuring how often the endpoint is functioning correctly – not simply if it's running. Options A, C, and D are related to infrastructure or cost but don't represent the core meaning of an SLA.
12 / 30
// Slack Message from SRE
SRE: "Hey @product_manager, just wanted to flag that a 99.99% availability SLO for this API would require significant architectural changes and increased operational overhead. It's a substantial investment."
The SRE's message focuses on 'substantial investment,' indicating that achieving 99.99% availability would demand considerable resources – primarily related to architecture and operations. Options A and C are incorrect; the SRE isn't immediately proposing or requesting a project. Option D is irrelevant to the core message.
13 / 30
{
"status": "error",
"code": 503,
"message": "Service Unavailable - Target availability of 99.99% was not met for the past hour."
}
What does the message in this API response primarily indicate?
The message 'Service Unavailable – Target availability of 99.99% was not met…' directly correlates to a violation of the service's SLO. When an SLO isn't achieved, services often temporarily become unavailable as a protective measure. Options A and D are incorrect, and option C addresses network issues.
14 / 30
'Implemented enhanced error handling and retry logic for the order processing service. This change is expected to improve availability to 99.95% over a rolling 30-day window.'
What does 'rolling 30-day window' signify in this PR description?
'Rolling' in this context means that the availability calculation isn't based on a single snapshot in time. Instead, it continuously updates its measurement using data from the preceding 30-day period – ensuring a more accurate reflection of recent performance. Options A and C are misinterpretations; option D is related to code review timing.
15 / 30
"We're currently focused on stabilizing the payment processing service after a recent spike in error rates. We've implemented some initial mitigation strategies, but we're still investigating the root cause and haven't yet achieved our 99.9% availability target."
The SRE's update clearly states that they haven't achieved their target availability – indicating an issue. It highlights their focus on investigation and mitigation. Options A and B are incorrect; option D is a request for resources, not a status report.
16 / 30
// Code Review Comment
"This endpoint currently has a 99.95% availability SLA. The team is pushing for 99.99%. Can we discuss the impact of this change on our monitoring and alerting strategy?"
What does 'availability SLA' refer to in this code review comment?
'Availability SLA' (Service Level Agreement) specifically defines the target percentage of uptime for a service. In this context, it's measuring how often the endpoint is functioning correctly – not simply if it's running. Options A, C, and D are related to infrastructure or cost but don't represent the core meaning of an SLA.
17 / 30
// Slack Message from SRE
SRE: "Hey @product_manager, just wanted to flag that a 99.99% availability SLO for this API would require significant architectural changes and increased operational overhead. It's a substantial investment."
The SRE's message focuses on 'substantial investment,' indicating that achieving 99.99% availability would demand considerable resources – primarily related to architecture and operations. Options A and C are incorrect; the SRE isn't immediately proposing or requesting a project. Option D is irrelevant to the core message.
18 / 30
{
"status": "error",
"code": 503,
"message": "Service Unavailable - Target availability of 99.99% was not met for the past hour."
}
What does the message in this API response primarily indicate?
The message 'Service Unavailable – Target availability of 99.99% was not met…' directly correlates to a violation of the service's SLO. When an SLO isn't achieved, services often temporarily become unavailable as a protective measure. Options A and D are incorrect, and option C addresses network issues.
19 / 30
'Implemented enhanced error handling and retry logic for the order processing service. This change is expected to improve availability to 99.95% over a rolling 30-day window.'
What does 'rolling 30-day window' signify in this PR description?
'Rolling' in this context means that the availability calculation isn't based on a single snapshot in time. Instead, it continuously updates its measurement using data from the preceding 30-day period – ensuring a more accurate reflection of recent performance. Options A and C are misinterpretations; option D is related to code review timing.
20 / 30
"We're currently focused on stabilizing the payment processing service after a recent spike in error rates. We've implemented some initial mitigation strategies, but we're still investigating the root cause and haven't yet achieved our 99.9% availability target."
The SRE's update clearly states that they haven't achieved their target availability – indicating an issue. It highlights their focus on investigation and mitigation. Options A and B are incorrect; option D is a request for resources, not a status report.
21 / 30
// Code Review Comment
"This endpoint currently has a 99.95% availability SLA. The team is pushing for 99.99%. Can we discuss the impact of this change on our monitoring and alerting strategy?"
What does 'availability SLA' refer to in this code review comment?
'Availability SLA' (Service Level Agreement) specifically defines the target percentage of uptime for a service. In this context, it's measuring how often the endpoint is functioning correctly – not simply if it's running. Options A, C, and D are related to infrastructure or cost but don't represent the core meaning of an SLA.
22 / 30
// Slack Message from SRE
SRE: "Hey @product_manager, just wanted to flag that a 99.99% availability SLO for this API would require significant architectural changes and increased operational overhead. It's a substantial investment."
The SRE's message focuses on 'substantial investment,' indicating that achieving 99.99% availability would demand considerable resources – primarily related to architecture and operations. Options A and C are incorrect; the SRE isn't immediately proposing or requesting a project. Option D is irrelevant to the core message.
23 / 30
{
"status": "error",
"code": 503,
"message": "Service Unavailable - Target availability of 99.99% was not met for the past hour."
}
What does the message in this API response primarily indicate?
The message 'Service Unavailable – Target availability of 99.99% was not met…' directly correlates to a violation of the service's SLO. When an SLO isn't achieved, services often temporarily become unavailable as a protective measure. Options A and D are incorrect, and option C addresses network issues.
24 / 30
'Implemented enhanced error handling and retry logic for the order processing service. This change is expected to improve availability to 99.95% over a rolling 30-day window.'
What does 'rolling 30-day window' signify in this PR description?
'Rolling' in this context means that the availability calculation isn't based on a single snapshot in time. Instead, it continuously updates its measurement using data from the preceding 30-day period – ensuring a more accurate reflection of recent performance. Options A and C are misinterpretations; option D is related to code review timing.
25 / 30
"We're currently focused on stabilizing the payment processing service after a recent spike in error rates. We've implemented some initial mitigation strategies, but we're still investigating the root cause and haven't yet achieved our 99.9% availability target."
The SRE's update clearly states that they haven't achieved their target availability – indicating an issue. It highlights their focus on investigation and mitigation. Options A and B are incorrect; option D is a request for resources, not a status report.
26 / 30
// Code Review Comment
"This endpoint currently has a 99.95% availability SLA. The team is pushing for 99.99%. Can we discuss the impact of this change on our monitoring and alerting strategy?"
What does 'availability SLA' refer to in this code review comment?
'Availability SLA' (Service Level Agreement) specifically defines the target percentage of uptime for a service. In this context, it's measuring how often the endpoint is functioning correctly – not simply if it's running. Options A, C, and D are related to infrastructure or cost but don't represent the core meaning of an SLA.
27 / 30
// Slack Message from SRE
SRE: "Hey @product_manager, just wanted to flag that a 99.99% availability SLO for this API would require significant architectural changes and increased operational overhead. It's a substantial investment."
The SRE's message focuses on 'substantial investment,' indicating that achieving 99.99% availability would demand considerable resources – primarily related to architecture and operations. Options A and C are incorrect; the SRE isn't immediately proposing or requesting a project. Option D is irrelevant to the core message.
28 / 30
{
"status": "error",
"code": 503,
"message": "Service Unavailable - Target availability of 99.99% was not met for the past hour."
}
What does the message in this API response primarily indicate?
The message 'Service Unavailable – Target availability of 99.99% was not met…' directly correlates to a violation of the service's SLO. When an SLO isn't achieved, services often temporarily become unavailable as a protective measure. Options A and D are incorrect, and option C addresses network issues.
29 / 30
'Implemented enhanced error handling and retry logic for the order processing service. This change is expected to improve availability to 99.95% over a rolling 30-day window.'
What does 'rolling 30-day window' signify in this PR description?
'Rolling' in this context means that the availability calculation isn't based on a single snapshot in time. Instead, it continuously updates its measurement using data from the preceding 30-day period – ensuring a more accurate reflection of recent performance. Options A and C are misinterpretations; option D is related to code review timing.
30 / 30
"We're currently focused on stabilizing the payment processing service after a recent spike in error rates. We've implemented some initial mitigation strategies, but we're still investigating the root cause and haven't yet achieved our 99.9% availability target."
The SRE's update clearly states that they haven't achieved their target availability – indicating an issue. It highlights their focus on investigation and mitigation. Options A and B are incorrect; option D is a request for resources, not a status report.
What will I learn from the "SLO Negotiation Language — SLO Engineering English | CoderLingo" exercise?
Practice the English vocabulary for SLO negotiation: discussing targets with product teams, explaining reliability investment costs, baseline-setting language, and iterative SLO refinement.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 30 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this SLO Engineering exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss slo engineering topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 30 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more SLO Engineering exercises?
See the full SLO Engineering exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.