What does an incident severity level (SEV) represent?
Severity levels classify incidents by business impact and urgency so the organization responds proportionately. A common scale: SEV1 — critical, widespread outage or data loss, all-hands response; SEV2 — major functionality broken for many users; SEV3 — partial/degraded impact; SEV4 — minor issue, low urgency. Severity drives everything downstream: who is paged, whether an incident commander is assigned, communication cadence, and whether a postmortem is required. Clear, agreed criteria prevent debates about severity during an incident, when speed matters most.
2 / 5
What is the role of an incident commander (IC)?
The incident commander owns the coordination of the response, not the technical fix. Borrowed from emergency services' Incident Command System, the IC maintains the big picture, makes and delegates decisions, prevents duplicated or conflicting efforts, and ensures communication flows. Critically, the IC should not be heads-down debugging — that is the job of subject-matter experts (the "ops" or resolver role). Separating coordination from hands-on work keeps the response organized, especially in large SEV1s where many people are involved and chaos is the default.
3 / 5
What is the communications lead role in incident response?
In a significant incident, the communications lead (or "comms lead"/scribe) handles the flow of information outward and keeps a timeline. They post regular updates to the status page, brief leadership and support teams, and translate technical status into stakeholder-appropriate language. This role is vital because, without it, either responders get constantly interrupted by "what's the status?" questions (slowing the fix) or stakeholders are left in the dark (eroding trust). Separating comms from the technical resolution lets each role do its job well.
4 / 5
What is the SBAR framework for incident communication?
SBAR (originally from healthcare/aviation) is a structured handoff format that keeps incident updates clear and complete: Situation (what is happening right now), Background (relevant context leading up to it), Assessment (what we think the cause/impact is), and Recommendation (what we propose to do or need). Using a consistent structure prevents rambling, ensures no critical element is omitted, and is especially valuable for shift handoffs or when escalating — the receiver gets exactly the information they need to act, fast.
5 / 5
What is a "blameless postmortem" and why is it used?
A blameless postmortem examines an incident to understand the systemic contributing factors — gaps in tooling, process, monitoring, or design — rather than finding someone to punish. The rationale is practical, not merely kind: if people fear blame, they hide details, omit their mistakes, and the organization fails to learn, so the same failure recurs. Blamelessness assumes people acted reasonably given what they knew, and asks how the system let a reasonable action lead to failure. The output is concrete, owned action items — not a scapegoat.
What does the "Incident Severity & Roles" vocabulary exercise cover?
This exercise tests real IT vocabulary related to incident severity & roles through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — this module shares real-world context with 9 other vocabulary modules. See "Related vocabulary" below to keep building a connected skill set.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.