What is the purpose of incident severity levels such as Sev1, Sev2, and Sev3?

• A. They calibrate incident response workflows and notification thresholds
• B. They classify impact and urgency to drive prioritization and escalation
• C. They track user login attempts
• D. They measure network bandwidth

Answer: (B)

The idea being tested is how severity levels help teams respond effectively. Severity levels categorize an incident by its impact and urgency, so the team can decide what to work on first and what needs to be escalated. That is exactly what Sev1, Sev2, and Sev3 are for: they map how bad an issue is and how quickly it must be addressed, which drives prioritization and escalation decisions.

In practice, a Sev1 incident typically means a critical outage or service could be down for many users, demanding immediate attention; Sev2 indicates a significant issue with noticeable impact but not a complete outage; Sev3 covers lower-impact problems or inconveniences. This classification keeps everyone aligned on what to fix first and who should be alerted.

These levels aren’t about logging attempts or measuring bandwidth, which are separate metrics or security/performance concerns. They’re about sizing the incident so responses are timely and appropriately resourced.