4 exercises — write public status page updates in plain, trustworthy English from first detection through resolution and post-incident follow-up.
0 / 14 completed
1 / 14
Ten minutes into an active outage, engineering has not yet found the root cause. Which is the best first public status page update?
The first public update should be posted early, use plain, non-technical language, and commit to a specific update cadence — even before the root cause is known.
Formula: "We are currently investigating [symptom in plain language]. We will post an update within [time]."
Never post internal technical detail (stack traces, table names, service names) on a public status page — customers don't need or want it, and it can leak sensitive infrastructure information. Committing to a specific next-update time (not "soon") builds trust even when there's nothing new to report.
2 / 14
The root cause has now been found: a bad deployment caused a database connection leak. Which status update is appropriate for customers?
Once the cause is understood, communicate the state ("root cause identified") and the expected resolution timeline — but still omit internal technical specifics (commit hashes, table names) and never assign individual blame publicly.
Formula: "The root cause has been identified and a fix is being [deployed/tested]. We expect [service] to be [restored/stable] within [timeframe]."
If you cannot give a confident timeframe, say so honestly: "We are working on a fix and will update within 20 minutes" rather than guessing a number you might miss.
3 / 14
The fix has been deployed and error rates have dropped to zero for the last 10 minutes. Which resolution message is correctly worded?
Best practice separates two distinct states: "fix deployed, monitoring" and "fully resolved." Prematurely marking an incident "resolved" and then having it recur damages trust more than a longer, honest monitoring period.
Sequence: 1. "The fix has been deployed. We are monitoring to confirm full recovery." (immediately after deploy) 2. "All systems are operational. Incident resolved at [time] UTC. Total duration: [X]." (after a stable monitoring window, typically 15–30 minutes)
This two-step pattern is standard across major status pages (Statuspage, Cachet) and sets correct customer expectations.
4 / 14
A frustrated customer replies to the status page asking "why didn't you catch this sooner?" What is the most professional public response tone?
Public responses to frustrated customers should acknowledge the impact without being defensive, and point to a concrete accountability mechanism (a post-incident review) rather than making excuses.
Useful phrases: "We understand the frustration/inconvenience this caused.", "We take reliability seriously and are reviewing what happened.", "We will share a summary of the root cause and preventive steps." Avoid deflecting blame publicly (vendors, "bad luck") even if partially true — it reads as excuse-making rather than ownership.
5 / 14
Sarah, a Senior Developer, is reviewing a pull request for a new customer authentication service. The PR description reads: 'Implemented OAuth 2.0 flow with refresh tokens.' During the review, she notices the code doesn't handle expired refresh tokens gracefully. Which of the following should Sarah add to her comment?
Sarah needs to provide specific guidance for improvement. Option 1 is irrelevant to the technical issue. Option 2 directly addresses the missing functionality – handling expired tokens and retries – which is crucial for a robust authentication service. Options 3 and 4 are too high-level and don't pinpoint the problem.
6 / 14
Mark, a Support Engineer, is drafting a Slack message to inform customers about an ongoing issue with their account status updates. The API response indicates 'High Latency' affecting status retrieval. Which of the following best reflects Mark's tone and content in this message?
Mark needs to be transparent about the severity of the issue. Option 1 downplays the problem too much. Option 2 is honest and proactive, acknowledging the impact on customers while communicating ongoing efforts. Options 3 and 4 are misleading and don't reflect the API response (High Latency). Honesty builds trust.
7 / 14
David, a DevOps Engineer, is writing a PR description for a deployed fix that resolved intermittent customer status updates. The previous issue caused sporadic timeouts during the retrieval process. Which of the following best describes the appropriate wording for David's message?
David needs to clearly state the problem solved and the technical approach. Option 1 is too vague. Option 2 accurately describes the root cause (timeouts) and the solution (caching), providing context for the change. Options 3 and 4 are irrelevant to the issue at hand.
8 / 14
Ben, a Lead Developer, is giving a standup update on an incident. The team has identified that a recent code change introduced a race condition leading to intermittent failures in customer status updates. Which of the following statements would be MOST effective for Ben to include?
Ben needs to clearly explain the root cause and the solution. Option 1 minimizes the severity of the issue. Option 2 accurately describes the technical problem (race condition) and the corrective action (locking mechanisms). Options 3 and 4 are too generic and don't convey the necessary information about the incident.
9 / 14
Sarah, a Senior Developer, is reviewing a pull request for a new customer authentication service. The PR description reads: 'Implemented OAuth 2.0 flow with refresh tokens.' During the review, she notices the code doesn't handle expired refresh tokens gracefully. Which of the following should Sarah add to her comment?
Sarah needs to provide specific guidance for improvement. Option 1 is irrelevant to the technical issue. Option 2 directly addresses the missing functionality – handling expired tokens and retries – which is crucial for a robust authentication service. Options 3 and 4 are too high-level and don't pinpoint the problem.
10 / 14
Mark, a Support Engineer, is drafting a Slack message to inform customers about an ongoing issue with their account status updates. The API response indicates 'High Latency' affecting status retrieval. Which of the following best reflects Mark's tone and content in this message?
Mark needs to be transparent about the severity of the issue. Option 1 downplays the problem too much. Option 2 is honest and proactive, acknowledging the impact on customers while communicating ongoing efforts. Options 3 and 4 are misleading and don't reflect the API response (High Latency). Honesty builds trust.
11 / 14
David, a DevOps Engineer, is writing a PR description for a deployed fix that resolved intermittent customer status updates. The previous issue caused sporadic timeouts during the retrieval process. Which of the following best describes the appropriate wording for David's message?
David needs to clearly state the problem solved and the technical approach. Option 1 is too vague. Option 2 accurately describes the root cause (timeouts) and the solution (caching), providing context for the change. Options 3 and 4 are irrelevant to the issue at hand.
12 / 14
Ben, a Lead Developer, is giving a standup update on an incident. The team has identified that a recent code change introduced a race condition leading to intermittent failures in customer status updates. Which of the following statements would be MOST effective for Ben to include?
Ben needs to clearly explain the root cause and the solution. Option 1 minimizes the severity of the issue. Option 2 accurately describes the technical problem (race condition) and the corrective action (locking mechanisms). Options 3 and 4 are too generic and don't convey the necessary information about the incident.
13 / 14
John, a Support Engineer, is responding to a customer via email who reports intermittent errors retrieving their account status. The API logs show repeated '503 Service Unavailable' responses. Which of the following statements would be MOST appropriate for his initial reply?
Option A provides a reassuring statement acknowledging the problem and indicating action while setting expectations for resolution. Options B and C are too vague and avoid responsibility; they don't offer any specific information or timeframe. Option D is unacceptable because it shifts blame and doesn't demonstrate understanding of the customer's issue – a key element of good incident response.
14 / 14
Emily, a DevOps Engineer, is writing a PR description for a deployed fix that addresses intermittent failures in retrieving customer status updates. The original issue involved stale session data causing timeouts. She wants to clearly communicate the resolution to stakeholders. Which of the following options best reflects this?
Option 2 accurately describes the core issue and solution – specifically addressing 'stale session data' and its impact on timeouts. Options A is too generic; B focuses on a technical detail without context, and C provides an overly simplified explanation. D shifts the focus to database optimization which wasn't the root cause.
What will I practise in "Customer Status Updates — Incident Response English Exercise"?
Practise writing public status page updates during an outage: plain-language incident messages, resolution wording, and customer-facing accountability tone. 4 exercises.
How many exercises are in this module?
This module has 14 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.