4 exercises — write clear, structured incident announcements, updates, and resolution messages when production is down.
0 / 9 completed
1 / 9
Production payment service is returning 500 errors for 30% of users since 14:32 UTC. You are the Incident Commander. Which Slack message best declares the incident?
Option B follows the industry-standard incident announcement format. It contains all required elements:
• [P1 INCIDENT] — severity + incident label visible at a glance • 🔴 — visual severity indicator • What is broken — payment service, 500 errors • Scope — 30% of users since 14:32 UTC • Business impact — ~6,000 transactions/hr • Incident Commander — clear owner (@alex) • Bridge link — where to join the response call • Status — "Investigating now"
Compare Option A — too casual, no structure. Options C and D lack scope, IC, and bridge. During an incident, the initial announcement sets the tone. A well-structured one means engineers can get up to speed instantly — seconds matter.
2 / 9
You're posting a status update 15 minutes into the incident. Complete the update: "14:47 UTC — Root cause identified: DB connection pool exhausted after config change deployed at 14:28. _____ Estimated recovery: 10–15 minutes."
"Rolling back the config change now." is the ideal update because it states the action in progress with the active present tense ("Rolling back"), which signals that work is actively happening right now.
Incident updates must follow a strict format: timestamp → status → root cause → action being taken → ETA. Every update should move the story forward. "We are trying to fix it" is vague (what specifically?). "Someone is working on this" doesn't say what they're doing.
Key language patterns for incident updates: • "Rolled back [X]" — past tense, completed • "Rolling back [X] now" — in progress • "Deploying hotfix for [X]" — in progress • "Monitoring recovery metrics" — observation phase
3 / 9
The incident is resolved. Which closing message is best?
Option C is the model resolution message. It contains:
• [RESOLVED] 🟢 — clear status change; people scanning channels see it instantly • Timestamp — when it was resolved (important for timeline and SLA calculation) • What was restored — payment service • How it was fixed — rolled back config change • Confirmation — P99 latency back to baseline (proves recovery is real) • Next step — post-mortem scheduled
The resolution message is the final formal communication about the incident. All engineering postmortems, SLA calculations, and customer communications reference it. Options A, B, and D are adequate for a casual fix but not for a production P1 incident.
4 / 9
During an incident bridge call, the database issue requires a specialist. How should you escalate?
Option C demonstrates effective escalation communication. Key elements:
• "Escalating to DB team" — names the escalation clearly for the channel log • Direct mention — @maria (specific person, not vague) • Context included — what the problem is and what was already tried • Bridge link — the expert knows exactly where to go
In incident response, vague escalations ("we need a DBA") lose precious minutes while people figure out who should respond, where to join, and what they're walking into. A good escalation message should let the expert understand the situation in 5 seconds and join the call ready to contribute.
5 / 9
Sarah, the Senior DevOps Engineer, is leading the response to a critical outage impacting the user authentication service. A monitoring alert triggered at 14:35 UTC indicating a spike in error rates. Which Slack message would be most appropriate for her initial communication to the on-call team?
'We're seeing high error rates with auth – investigating.'
This message provides clear and concise information about the severity of the issue (critical), the affected service (auth), the timing of the alert (14:35 UTC), and indicates immediate investigation. Option A is too dramatic, option C lacks specific details, and option D denies the problem which is unhelpful during an outage.
6 / 9
David, a junior developer, has submitted a pull request to update the retry logic for failed API calls. The PR description reads: 'Fixed bug'. Review David's comment on his own code. Which of the following responses is MOST effective in guiding him towards more detailed communication during an outage?
'Can you add a brief explanation of why the retries were failing and what the new logic does?'
Option 3 directly prompts David to provide crucial context – the root cause of the failures and how the revised retry logic works. This is essential during an outage to understand the problem and prevent recurrence. Options A and C are too brief, while option B focuses solely on logging without addressing the core issue.
7 / 9
The API endpoint for retrieving user order history is experiencing intermittent 503 errors. The monitoring system returns this JSON response: `{"status": "503", "message": "Service Unavailable", "timestamp": "2024-10-27T15:00:00Z"}`. Which of the following actions should you document in the incident report, directly referencing this response?
'The service was unavailable due to high load.'
This response accurately describes the information contained within the provided API response – the 503 status code, message, and timestamp. It's crucial to precisely record these details for troubleshooting and analysis. Options A is a vague interpretation, while options C and D are misleading.
8 / 9
During the daily stand-up meeting, you're reporting on the ongoing outage. Your update is: 'We've identified a database connection issue.' Maria, the team lead, asks for more detail. Which of the following responses would be MOST appropriate to provide?
'The database was overloaded.'
Option 2 provides specific information about the root cause – the database connection pool exhaustion. This is far more useful than a general statement like 'the database was overloaded' (option A) or a vague description of problems (options C and D). It demonstrates understanding and facilitates further discussion.
9 / 9
The on-call engineer, Ben, is coordinating the response to a major outage. He needs to escalate the issue to the database team. Which communication strategy should he employ?
'Let them know we need their immediate assistance.'
Option 1 outlines the best practice for escalating during an outage – a formal request with comprehensive information (logs and impact assessment). This ensures the database team understands the severity of the issue and can prioritize their response appropriately. Options A and C are too informal, while option B leaves it to chance.
What will I practise in "Communicating During an Outage — Incident Response English Exercise"?
Practice writing incident announcements, status updates, escalations, and resolution messages under pressure. 4 exercises for SRE, DevOps, and backend engineers.
How many exercises are in this module?
This module has 9 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 Response exercises?
Browse the full Incident Response 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.