Practice English vocabulary for major incident management: SEV-1 process, incident commanders, incident bridges, SLO-based resolution, and leadership summaries.
0 / 15 completed
1 / 15
What does 'the major incident process kicks in at SEV-1' mean?
Organizations define severity tiers (SEV-1 through SEV-4 or similar). SEV-1 represents the most critical incidents — full service outages, data loss, security breaches. The major incident process brings additional structure, resources, and visibility to drive fast resolution.
2 / 15
What does 'the incident commander coordinates the response'?
The Incident Commander (IC) role is borrowed from emergency management. The IC owns the process, not the technical solution. They assign tasks, keep the response organized, prevent people from working at cross-purposes, and drive toward resolution.
3 / 15
What is 'an incident bridge' and why is it opened immediately?
An incident bridge (or war room call) brings all responders together in real time. Voice/video communication is faster than typed chat for crisis coordination. Opening it immediately prevents responders from working in silos and delays caused by slow async communication.
4 / 15
What does 'the incident is declared resolved when the SLO is met' mean?
Declaring resolution based on SLO recovery ensures the service is genuinely restored, not just superficially patched. If the error rate SLO is 99.9%, resolution requires the error rate to return below 0.1% — a fix that only partially works does not meet the resolution criteria.
5 / 15
What is 'the 24-hour summary sent to leadership'?
Leadership summaries for major incidents provide executives with the key facts without technical jargon: business impact (customers affected, revenue loss), timeline, resolution actions, and next steps. They enable informed decisions about customer communication, regulatory reporting, and resource allocation.
6 / 15
During a code review of the new payment processing service, Alice comments: 'This retry logic seems overly aggressive; it's triggering every 50ms. We need to investigate if this is causing downstream issues.' What does Alice likely mean by 'overly aggressive' in this context?
Alice is referring to a potential problem with the frequency of retries. 'Overly aggressive' suggests the retry logic is attempting too many corrections in a short period, which can exacerbate the issue and lead to cascading failures. The code snippet shows the interval itself, highlighting the point of concern.
7 / 15
In a Slack channel dedicated to the 'Phoenix' microservice outage, Ben writes: 'We've escalated this to Level 2. The incident bridge is open and we're coordinating with SREs across all teams.' What is the primary purpose of an 'incident bridge'?
An 'incident bridge' is a dedicated channel or meeting space designed for rapid communication and coordination during an active incident. This allows teams to share updates, identify dependencies, and collectively address the problem efficiently – it's not about formal documentation or monitoring tools.
8 / 15
Sarah is drafting a PR description for a fix to a database connection issue. She writes: 'Fixed a race condition that was intermittently causing connection timeouts. The solution involved adding a retry mechanism with exponential backoff.' What does 'exponential backoff' refer to?
Exponential backoff is a common technique used to handle transient errors like connection timeouts. It involves increasing the delay between retry attempts after each failure, preventing the system from overwhelming the service with repeated requests and allowing it time to recover. This avoids creating new problems.
9 / 15
During a standup meeting about the 'Hydra' application deployment, David states: 'We're seeing increased latency after the recent upgrade. The SLO for response time is currently being violated.' What does 'violating an SLO' indicate?
An SLO (Service Level Objective) defines the acceptable level of performance for a system. 'Violating an SLO' means that the actual performance metrics – in this case, response time latency – are exceeding the defined target, indicating a serious issue requiring immediate attention.
10 / 15
Mark is writing a post-incident report for the 'Cerberus' system failure. He states: 'Following the incident, we sent a 24-hour summary to leadership outlining the key findings and recommended actions.' What was the purpose of this summary?
The 24-hour summary is intended to provide a high-level update to leadership on the critical aspects of the incident – what happened, its impact (e.g., user disruption), and the immediate steps being taken to address it. It's about communication, not deep technical detail.
11 / 15
During a code review of the new payment processing service, Alice comments: 'This retry logic seems overly aggressive; it's triggering every 50ms. We need to investigate if this is causing downstream issues.' What does Alice likely mean by 'overly aggressive' in this context?
Alice is referring to a potential problem with the frequency of retries. 'Overly aggressive' suggests the retry logic is attempting too many corrections in a short period, which can exacerbate the issue and lead to cascading failures. The code snippet shows the interval itself, highlighting the point of concern.
12 / 15
In a Slack channel dedicated to the 'Phoenix' microservice outage, Ben writes: 'We've escalated this to Level 2. The incident bridge is open and we're coordinating with SREs across all teams.' What is the primary purpose of an 'incident bridge'?
An 'incident bridge' is a dedicated channel or meeting space designed for rapid communication and coordination during an active incident. This allows teams to share updates, identify dependencies, and collectively address the problem efficiently – it's not about formal documentation or monitoring tools.
13 / 15
Sarah is drafting a PR description for a fix to a database connection issue. She writes: 'Fixed a race condition that was intermittently causing connection timeouts. The solution involved adding a retry mechanism with exponential backoff.' What does 'exponential backoff' refer to?
Exponential backoff is a common technique used to handle transient errors like connection timeouts. It involves increasing the delay between retry attempts after each failure, preventing the system from overwhelming the service with repeated requests and allowing it time to recover. This avoids creating new problems.
14 / 15
During a standup meeting about the 'Hydra' application deployment, David states: 'We're seeing increased latency after the recent upgrade. The SLO for response time is currently being violated.' What does 'violating an SLO' indicate?
An SLO (Service Level Objective) defines the acceptable level of performance for a system. 'Violating an SLO' means that the actual performance metrics – in this case, response time latency – are exceeding the defined target, indicating a serious issue requiring immediate attention.
15 / 15
Mark is writing a post-incident report for the 'Cerberus' system failure. He states: 'Following the incident, we sent a 24-hour summary to leadership outlining the key findings and recommended actions.' What was the purpose of this summary?
The 24-hour summary is intended to provide a high-level update to leadership on the critical aspects of the incident – what happened, its impact (e.g., user disruption), and the immediate steps being taken to address it. It's about communication, not deep technical detail.
What will I practise in "Major Incident Vocabulary"?
Practice English vocabulary for major incident management: SEV-1 process, incident commanders, incident bridges, SLO-based resolution, and leadership summaries.
How many exercises are in this module?
This module has 15 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
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.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Incident Command Language exercises?
Browse the full Incident Command Language hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.