Learn precise vocabulary for communicating partial outages and service degradation.
0 / 14 completed
1 / 14
What is the difference between 'partial outage' and 'degraded performance'?
Partial outage means specific features or user groups cannot use the service at all. Degraded performance means the service works but is slow, unreliable, or producing errors at a higher-than-normal rate.
2 / 14
What does 'under investigation' mean on a status page?
'Under investigation' means the team is aware of the incident and actively working to identify the cause — the root cause is not yet known.
3 / 14
Which phrase correctly describes a situation where only EU users are affected?
Region-specific impact should be described precisely: 'Users in the EU region are experiencing...' — this helps users in other regions know they are not affected.
4 / 14
What does 'error rate' mean in incident communication?
Error rate is the percentage of requests returning errors (e.g., 5xx responses) versus successful responses. During a degradation, the error rate rises above its baseline.
5 / 14
What is the meaning of 'elevated latency' in a status update?
Elevated latency means the service is responding, but much more slowly than normal. Users experience slow load times, timeouts, or sluggish performance.
6 / 14
Code Review Comment
During a code review of the new payment API, Sarah left this comment: 'I'm seeing intermittent failures when processing transactions for users in Brazil. The response times are significantly higher than expected, and occasionally we get a 502 error. This seems to be impacting user experience.' Which of the following best describes Sarah's observation regarding service degradation?
Sarah's comment describes a partial outage. This isn't a complete system failure (option B), but rather a situation where the service is only partially functioning correctly for some users or under certain conditions (like geographic location). 'High availability' (option A) implies consistent access, which isn't present here due to the intermittent failures and elevated latency. 'Optimal performance' (option D) contradicts the reported response times, and a 502 error indicates a fundamental problem preventing successful requests.
7 / 14
Code Review Comment
During a code review of the new payment API, Sarah left this comment: 'I'm seeing intermittent failures when processing transactions for users in Brazil. The response times are significantly higher than expected, and occasionally we get a 502 error. This seems to be impacting user experience.' Which of the following best describes Sarah's observation regarding service degradation?
Sarah's comment describes a partial outage. This isn't a complete system failure (option B), but rather a situation where the service is only partially functioning correctly for some users or under certain conditions (like geographic location). 'High availability' (option A) implies consistent access, which isn't present here due to the intermittent failures and elevated latency. 'Optimal performance' (option D) contradicts the reported response times, and a 502 error indicates a fundamental problem preventing successful requests.
8 / 14
Code Review Comment
During a code review of the new payment API, Sarah left this comment: 'I'm seeing intermittent failures when processing transactions for users in Brazil. The response times are significantly higher than expected, and occasionally we get a 502 error. This seems to be impacting user experience.' Which of the following best describes Sarah's observation regarding service degradation?
Sarah's comment describes a partial outage. This isn't a complete system failure (option B), but rather a situation where the service is only partially functioning correctly for some users or under certain conditions (like geographic location). 'High availability' (option A) implies consistent access, which isn't present here due to the intermittent failures and elevated latency. 'Optimal performance' (option D) contradicts the reported response times, and a 502 error indicates a fundamental problem preventing successful requests.
9 / 14
Code Review Comment
During a code review of the new payment API, Sarah left this comment: 'I'm seeing intermittent failures when processing transactions for users in Brazil. The response times are significantly higher than expected, and occasionally we get a 502 error. This seems to be impacting user experience.' Which of the following best describes Sarah's observation regarding service degradation?
Sarah's comment describes a partial outage. This isn't a complete system failure (option B), but rather a situation where the service is only partially functioning correctly for some users or under certain conditions (like geographic location). 'High availability' (option A) implies consistent access, which isn't present here due to the intermittent failures and elevated latency. 'Optimal performance' (option D) contradicts the reported response times, and a 502 error indicates a fundamental problem preventing successful requests.
10 / 14
During a code review of the user authentication service, Liam left this comment: 'We're experiencing increased latency during peak hours. The average response time for login requests has jumped from 20ms to 150ms. I suspect this might be related to our database scaling limits.' Which phrase best describes Liam's observation?
// No code provided
Liam correctly identifies 'elevated latency' as the core issue. The increased response time (150ms vs. 20ms) clearly indicates a performance bottleneck. Options A, C, and D are potential causes of latency but aren't directly described in Liam's comment.
11 / 14
In a Slack channel for the production monitoring team, Maya posted: 'The API gateway is reporting increased error rates (5%) during the last hour. We're investigating.' What does 'increased error rates' typically signify in this context?
// No code provided
'Increased error rates' directly refers to more requests encountering failures. This is a key indicator of service degradation or problems within the system. Options A, C and D describe alternative scenarios that wouldn't be reflected in an error rate increase.
12 / 14
The following API response was received from the order processing service:
HTTP/1.1 503 Service Unavailable
Content-Type: application/json
{
"status": "error",
"message": "Service temporarily unavailable due to high load."
}
What does the 'Service Unavailable' status code and associated message suggest about the order processing service?
// No code provided
A '503 Service Unavailable' status code indicates that the server itself is temporarily unable to handle requests. The message confirms this, pointing to high load as a likely cause of degradation. Options A and C represent alternative scenarios—the service isn't malfunctioning, nor are there critical bugs.
13 / 14
During the code review for a new feature that allows users to upload large files, David wrote in the PR description: 'This change introduces optimized caching strategies. However, we've observed occasional spikes in latency when processing uploads exceeding 10MB.' What does David's comment primarily highlight?
// No code provided
David's comment focuses on the specific impact of large uploads – latency spikes. This suggests that the caching strategy, while intended to improve performance, is being overwhelmed by these particular workloads, indicating a degradation point related to file size.
14 / 14
During the daily stand-up meeting, Sarah reported: 'We're seeing intermittent timeouts when users from Germany attempt to access the reporting dashboard. The response times are consistently above 5 seconds.' What does 'intermittent timeouts' suggest about the system's behavior?
// No code provided
'Intermittent timeouts' strongly implies that the problem isn't consistent but occurs sporadically. This typically points to a localized issue – in this case, Germany – where network conditions or server load are causing delays for specific users. Options A and D are incorrect because they describe broader issues.
What does the "Service Degradation — Vocabulary and Language" exercise cover?
Learn precise vocabulary for communicating partial outages and service degradation.
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.
How many questions are in "Service Degradation — Vocabulary and Language"?
This exercise has 14 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more External Crisis Communication exercises?
Browse the full External Crisis Communication hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.