Customer-Facing Post-Incident Summary — Writing Vocabulary
Write clear, trustworthy customer-facing post-incident summaries.
0 / 45 completed
1 / 45
What is a 'customer-facing post-incident summary'?
A customer-facing post-incident summary is a public or semi-public document that explains the incident in plain language — what happened, impact, root cause summary, and prevention steps.
2 / 45
Which sections are standard in a customer-facing incident summary?
A customer-facing incident summary typically includes: Summary, Timeline, Root Cause (in accessible language), Impact, and What We Are Doing / Preventive Actions.
3 / 45
How should root cause be described in a customer-facing summary?
Root cause in a customer-facing summary should be in plain English — 'A configuration change prevented our load balancer from routing traffic correctly' — not technical jargon.
4 / 45
What does 'what we are doing' communicate to customers?
'What we are doing' section lists concrete, specific preventive actions — 'We are adding automated deployment validation tests' — demonstrating accountability and action.
5 / 45
What tone should a customer-facing post-incident summary use?
The correct tone is transparent, accountable, and forward-looking. Customers trust companies that acknowledge failures honestly and explain credible preventive measures.
6 / 45
Slack message:
"@john.doe just reported a 500 error on the `/users/create` endpoint. Users are unable to create new accounts. Initial investigation suggests it might be related to a recent change in the database schema validation logic. We're monitoring."This scenario focuses on communicating an incident effectively. The best response clearly states the problem (500 error on endpoint), acknowledges the potential cause (schema validation change), and confirms ongoing monitoring – all vital elements of a customer-facing update. Options A and C are incorrect because they lack key information, while option D is too technical for a non-technical audience. Option B is partially correct but doesn't fully capture the need to provide context.
7 / 45
PR Description
Subject: Critical Outage - User Account Creation
We experienced a significant outage affecting user account creation today. Users reported encountering a 500 error when attempting to create new accounts. Our initial investigation points towards an issue with the database schema validation, specifically a recent update to the `validate_user_data` function. We've deployed a rollback and are actively monitoring the system. Further updates will follow.
Which of the following best describes the primary purpose of this PR description for a customer-facing communication?This question tests understanding of the core purpose of a customer-facing post-incident summary. While technical details are important internally, the primary goal is to communicate clearly and concisely to users affected by the outage. Option B is incorrect because this description isn't meant for troubleshooting; that's handled through support channels. Option D focuses solely on the development team's actions, neglecting the customer's perspective – a crucial element of effective communication. The correct answer highlights the need to inform customers about the situation and ongoing remediation efforts.
8 / 45
Which of the following options best refines this message for a customer-facing update, focusing on clarity and minimizing alarm?
The original draft is vague and doesn't provide users with enough information to understand the severity of the issue or what they should do in the meantime. Option A correctly identifies this - it's insufficient because it lacks crucial details like impact and timeline. Options B and C are acceptable but don't fully address the need for proactive communication. Option D is too strong, as a 'full fix' isn't guaranteed at this stage.
9 / 45
A customer support team is preparing a summary for users affected by an outage impacting their ability to access key features in a SaaS application. The initial draft reads: "We experienced some issues with the backend services today, which temporarily prevented some users from accessing certain features. Our engineers are working to resolve this." Which of the following options represents the *most* effective revision of this message for direct communication to affected customers, prioritizing clarity and reassurance?
The correct answer (option 0) uses precise language – 'service disruption,' 'identified the cause' – demonstrating professionalism and providing a clear picture of the situation. It avoids vague terms like 'some issues' and offers reassurance about a solution without over-promising. Options B and D are too informal, while option C focuses solely on acknowledging the problem without outlining corrective actions.
10 / 45
A developer is drafting a post-incident summary for a critical outage affecting the API's ability to retrieve user profiles. The initial draft reads: 'Yesterday, we had some performance degradation impacting profile retrieval. We've optimized queries and are monitoring.' Which of the following options best refines this message for a customer-facing update, focusing on transparency and acknowledging impact?
The correct answer emphasizes transparency by acknowledging the *impact* of the degradation (affected retrieval times) and clearly stating what actions were taken (optimizations & monitoring). Options B and D are too dismissive or vague. Option C introduces unnecessary alarm without specific details, while option A provides a balanced and informative update suitable for customer communication.
11 / 45
Slack message:
"@john.doe just reported a 500 error on the `/users/create` endpoint. Users are unable to create new accounts. Initial investigation suggests it might be related to a recent change in the database schema validation logic. We're monitoring."This scenario focuses on communicating an incident effectively. The best response clearly states the problem (500 error on endpoint), acknowledges the potential cause (schema validation change), and confirms ongoing monitoring – all vital elements of a customer-facing update. Options A and C are incorrect because they lack key information, while option D is too technical for a non-technical audience. Option B is partially correct but doesn't fully capture the need to provide context.
12 / 45
PR Description
Subject: Critical Outage - User Account Creation
We experienced a significant outage affecting user account creation today. Users reported encountering a 500 error when attempting to create new accounts. Our initial investigation points towards an issue with the database schema validation, specifically a recent update to the `validate_user_data` function. We've deployed a rollback and are actively monitoring the system. Further updates will follow.
Which of the following best describes the primary purpose of this PR description for a customer-facing communication?This question tests understanding of the core purpose of a customer-facing post-incident summary. While technical details are important internally, the primary goal is to communicate clearly and concisely to users affected by the outage. Option B is incorrect because this description isn't meant for troubleshooting; that's handled through support channels. Option D focuses solely on the development team's actions, neglecting the customer's perspective – a crucial element of effective communication. The correct answer highlights the need to inform customers about the situation and ongoing remediation efforts.
13 / 45
Which of the following options best refines this message for a customer-facing update, focusing on clarity and minimizing alarm?
The original draft is vague and doesn't provide users with enough information to understand the severity of the issue or what they should do in the meantime. Option A correctly identifies this - it's insufficient because it lacks crucial details like impact and timeline. Options B and C are acceptable but don't fully address the need for proactive communication. Option D is too strong, as a 'full fix' isn't guaranteed at this stage.
14 / 45
A customer support team is preparing a summary for users affected by an outage impacting their ability to access key features in a SaaS application. The initial draft reads: "We experienced some issues with the backend services today, which temporarily prevented some users from accessing certain features. Our engineers are working to resolve this." Which of the following options represents the *most* effective revision of this message for direct communication to affected customers, prioritizing clarity and reassurance?
The correct answer (option 0) uses precise language – 'service disruption,' 'identified the cause' – demonstrating professionalism and providing a clear picture of the situation. It avoids vague terms like 'some issues' and offers reassurance about a solution without over-promising. Options B and D are too informal, while option C focuses solely on acknowledging the problem without outlining corrective actions.
15 / 45
A developer is drafting a post-incident summary for a critical outage affecting the API's ability to retrieve user profiles. The initial draft reads: 'Yesterday, we had some performance degradation impacting profile retrieval. We've optimized queries and are monitoring.' Which of the following options best refines this message for a customer-facing update, focusing on transparency and acknowledging impact?
The correct answer emphasizes transparency by acknowledging the *impact* of the degradation (affected retrieval times) and clearly stating what actions were taken (optimizations & monitoring). Options B and D are too dismissive or vague. Option C introduces unnecessary alarm without specific details, while option A provides a balanced and informative update suitable for customer communication.
16 / 45
Slack message:
"@john.doe just reported a 500 error on the `/users/create` endpoint. Users are unable to create new accounts. Initial investigation suggests it might be related to a recent change in the database schema validation logic. We're monitoring."This scenario focuses on communicating an incident effectively. The best response clearly states the problem (500 error on endpoint), acknowledges the potential cause (schema validation change), and confirms ongoing monitoring – all vital elements of a customer-facing update. Options A and C are incorrect because they lack key information, while option D is too technical for a non-technical audience. Option B is partially correct but doesn't fully capture the need to provide context.
17 / 45
PR Description
Subject: Critical Outage - User Account Creation
We experienced a significant outage affecting user account creation today. Users reported encountering a 500 error when attempting to create new accounts. Our initial investigation points towards an issue with the database schema validation, specifically a recent update to the `validate_user_data` function. We've deployed a rollback and are actively monitoring the system. Further updates will follow.
Which of the following best describes the primary purpose of this PR description for a customer-facing communication?This question tests understanding of the core purpose of a customer-facing post-incident summary. While technical details are important internally, the primary goal is to communicate clearly and concisely to users affected by the outage. Option B is incorrect because this description isn't meant for troubleshooting; that's handled through support channels. Option D focuses solely on the development team's actions, neglecting the customer's perspective – a crucial element of effective communication. The correct answer highlights the need to inform customers about the situation and ongoing remediation efforts.
18 / 45
Which of the following options best refines this message for a customer-facing update, focusing on clarity and minimizing alarm?
The original draft is vague and doesn't provide users with enough information to understand the severity of the issue or what they should do in the meantime. Option A correctly identifies this - it's insufficient because it lacks crucial details like impact and timeline. Options B and C are acceptable but don't fully address the need for proactive communication. Option D is too strong, as a 'full fix' isn't guaranteed at this stage.
19 / 45
A customer support team is preparing a summary for users affected by an outage impacting their ability to access key features in a SaaS application. The initial draft reads: "We experienced some issues with the backend services today, which temporarily prevented some users from accessing certain features. Our engineers are working to resolve this." Which of the following options represents the *most* effective revision of this message for direct communication to affected customers, prioritizing clarity and reassurance?
The correct answer (option 0) uses precise language – 'service disruption,' 'identified the cause' – demonstrating professionalism and providing a clear picture of the situation. It avoids vague terms like 'some issues' and offers reassurance about a solution without over-promising. Options B and D are too informal, while option C focuses solely on acknowledging the problem without outlining corrective actions.
20 / 45
A developer is drafting a post-incident summary for a critical outage affecting the API's ability to retrieve user profiles. The initial draft reads: 'Yesterday, we had some performance degradation impacting profile retrieval. We've optimized queries and are monitoring.' Which of the following options best refines this message for a customer-facing update, focusing on transparency and acknowledging impact?
The correct answer emphasizes transparency by acknowledging the *impact* of the degradation (affected retrieval times) and clearly stating what actions were taken (optimizations & monitoring). Options B and D are too dismissive or vague. Option C introduces unnecessary alarm without specific details, while option A provides a balanced and informative update suitable for customer communication.
21 / 45
Slack message:
"@john.doe just reported a 500 error on the `/users/create` endpoint. Users are unable to create new accounts. Initial investigation suggests it might be related to a recent change in the database schema validation logic. We're monitoring."This scenario focuses on communicating an incident effectively. The best response clearly states the problem (500 error on endpoint), acknowledges the potential cause (schema validation change), and confirms ongoing monitoring – all vital elements of a customer-facing update. Options A and C are incorrect because they lack key information, while option D is too technical for a non-technical audience. Option B is partially correct but doesn't fully capture the need to provide context.
22 / 45
PR Description
Subject: Critical Outage - User Account Creation
We experienced a significant outage affecting user account creation today. Users reported encountering a 500 error when attempting to create new accounts. Our initial investigation points towards an issue with the database schema validation, specifically a recent update to the `validate_user_data` function. We've deployed a rollback and are actively monitoring the system. Further updates will follow.
Which of the following best describes the primary purpose of this PR description for a customer-facing communication?This question tests understanding of the core purpose of a customer-facing post-incident summary. While technical details are important internally, the primary goal is to communicate clearly and concisely to users affected by the outage. Option B is incorrect because this description isn't meant for troubleshooting; that's handled through support channels. Option D focuses solely on the development team's actions, neglecting the customer's perspective – a crucial element of effective communication. The correct answer highlights the need to inform customers about the situation and ongoing remediation efforts.
23 / 45
Which of the following options best refines this message for a customer-facing update, focusing on clarity and minimizing alarm?
The original draft is vague and doesn't provide users with enough information to understand the severity of the issue or what they should do in the meantime. Option A correctly identifies this - it's insufficient because it lacks crucial details like impact and timeline. Options B and C are acceptable but don't fully address the need for proactive communication. Option D is too strong, as a 'full fix' isn't guaranteed at this stage.
24 / 45
A customer support team is preparing a summary for users affected by an outage impacting their ability to access key features in a SaaS application. The initial draft reads: "We experienced some issues with the backend services today, which temporarily prevented some users from accessing certain features. Our engineers are working to resolve this." Which of the following options represents the *most* effective revision of this message for direct communication to affected customers, prioritizing clarity and reassurance?
The correct answer (option 0) uses precise language – 'service disruption,' 'identified the cause' – demonstrating professionalism and providing a clear picture of the situation. It avoids vague terms like 'some issues' and offers reassurance about a solution without over-promising. Options B and D are too informal, while option C focuses solely on acknowledging the problem without outlining corrective actions.
25 / 45
A developer is drafting a post-incident summary for a critical outage affecting the API's ability to retrieve user profiles. The initial draft reads: 'Yesterday, we had some performance degradation impacting profile retrieval. We've optimized queries and are monitoring.' Which of the following options best refines this message for a customer-facing update, focusing on transparency and acknowledging impact?
The correct answer emphasizes transparency by acknowledging the *impact* of the degradation (affected retrieval times) and clearly stating what actions were taken (optimizations & monitoring). Options B and D are too dismissive or vague. Option C introduces unnecessary alarm without specific details, while option A provides a balanced and informative update suitable for customer communication.
26 / 45
Slack message:
"@john.doe just reported a 500 error on the `/users/create` endpoint. Users are unable to create new accounts. Initial investigation suggests it might be related to a recent change in the database schema validation logic. We're monitoring."This scenario focuses on communicating an incident effectively. The best response clearly states the problem (500 error on endpoint), acknowledges the potential cause (schema validation change), and confirms ongoing monitoring – all vital elements of a customer-facing update. Options A and C are incorrect because they lack key information, while option D is too technical for a non-technical audience. Option B is partially correct but doesn't fully capture the need to provide context.
27 / 45
PR Description
Subject: Critical Outage - User Account Creation
We experienced a significant outage affecting user account creation today. Users reported encountering a 500 error when attempting to create new accounts. Our initial investigation points towards an issue with the database schema validation, specifically a recent update to the `validate_user_data` function. We've deployed a rollback and are actively monitoring the system. Further updates will follow.
Which of the following best describes the primary purpose of this PR description for a customer-facing communication?This question tests understanding of the core purpose of a customer-facing post-incident summary. While technical details are important internally, the primary goal is to communicate clearly and concisely to users affected by the outage. Option B is incorrect because this description isn't meant for troubleshooting; that's handled through support channels. Option D focuses solely on the development team's actions, neglecting the customer's perspective – a crucial element of effective communication. The correct answer highlights the need to inform customers about the situation and ongoing remediation efforts.
28 / 45
Which of the following options best refines this message for a customer-facing update, focusing on clarity and minimizing alarm?
The original draft is vague and doesn't provide users with enough information to understand the severity of the issue or what they should do in the meantime. Option A correctly identifies this - it's insufficient because it lacks crucial details like impact and timeline. Options B and C are acceptable but don't fully address the need for proactive communication. Option D is too strong, as a 'full fix' isn't guaranteed at this stage.
29 / 45
A customer support team is preparing a summary for users affected by an outage impacting their ability to access key features in a SaaS application. The initial draft reads: "We experienced some issues with the backend services today, which temporarily prevented some users from accessing certain features. Our engineers are working to resolve this." Which of the following options represents the *most* effective revision of this message for direct communication to affected customers, prioritizing clarity and reassurance?
The correct answer (option 0) uses precise language – 'service disruption,' 'identified the cause' – demonstrating professionalism and providing a clear picture of the situation. It avoids vague terms like 'some issues' and offers reassurance about a solution without over-promising. Options B and D are too informal, while option C focuses solely on acknowledging the problem without outlining corrective actions.
30 / 45
A developer is drafting a post-incident summary for a critical outage affecting the API's ability to retrieve user profiles. The initial draft reads: 'Yesterday, we had some performance degradation impacting profile retrieval. We've optimized queries and are monitoring.' Which of the following options best refines this message for a customer-facing update, focusing on transparency and acknowledging impact?
The correct answer emphasizes transparency by acknowledging the *impact* of the degradation (affected retrieval times) and clearly stating what actions were taken (optimizations & monitoring). Options B and D are too dismissive or vague. Option C introduces unnecessary alarm without specific details, while option A provides a balanced and informative update suitable for customer communication.
31 / 45
Slack message:
"@john.doe just reported a 500 error on the `/users/create` endpoint. Users are unable to create new accounts. Initial investigation suggests it might be related to a recent change in the database schema validation logic. We're monitoring."This scenario focuses on communicating an incident effectively. The best response clearly states the problem (500 error on endpoint), acknowledges the potential cause (schema validation change), and confirms ongoing monitoring – all vital elements of a customer-facing update. Options A and C are incorrect because they lack key information, while option D is too technical for a non-technical audience. Option B is partially correct but doesn't fully capture the need to provide context.
32 / 45
PR Description
Subject: Critical Outage - User Account Creation
We experienced a significant outage affecting user account creation today. Users reported encountering a 500 error when attempting to create new accounts. Our initial investigation points towards an issue with the database schema validation, specifically a recent update to the `validate_user_data` function. We've deployed a rollback and are actively monitoring the system. Further updates will follow.
Which of the following best describes the primary purpose of this PR description for a customer-facing communication?This question tests understanding of the core purpose of a customer-facing post-incident summary. While technical details are important internally, the primary goal is to communicate clearly and concisely to users affected by the outage. Option B is incorrect because this description isn't meant for troubleshooting; that's handled through support channels. Option D focuses solely on the development team's actions, neglecting the customer's perspective – a crucial element of effective communication. The correct answer highlights the need to inform customers about the situation and ongoing remediation efforts.
33 / 45
Which of the following options best refines this message for a customer-facing update, focusing on clarity and minimizing alarm?
The original draft is vague and doesn't provide users with enough information to understand the severity of the issue or what they should do in the meantime. Option A correctly identifies this - it's insufficient because it lacks crucial details like impact and timeline. Options B and C are acceptable but don't fully address the need for proactive communication. Option D is too strong, as a 'full fix' isn't guaranteed at this stage.
34 / 45
A customer support team is preparing a summary for users affected by an outage impacting their ability to access key features in a SaaS application. The initial draft reads: "We experienced some issues with the backend services today, which temporarily prevented some users from accessing certain features. Our engineers are working to resolve this." Which of the following options represents the *most* effective revision of this message for direct communication to affected customers, prioritizing clarity and reassurance?
The correct answer (option 0) uses precise language – 'service disruption,' 'identified the cause' – demonstrating professionalism and providing a clear picture of the situation. It avoids vague terms like 'some issues' and offers reassurance about a solution without over-promising. Options B and D are too informal, while option C focuses solely on acknowledging the problem without outlining corrective actions.
35 / 45
A developer is drafting a post-incident summary for a critical outage affecting the API's ability to retrieve user profiles. The initial draft reads: 'Yesterday, we had some performance degradation impacting profile retrieval. We've optimized queries and are monitoring.' Which of the following options best refines this message for a customer-facing update, focusing on transparency and acknowledging impact?
The correct answer emphasizes transparency by acknowledging the *impact* of the degradation (affected retrieval times) and clearly stating what actions were taken (optimizations & monitoring). Options B and D are too dismissive or vague. Option C introduces unnecessary alarm without specific details, while option A provides a balanced and informative update suitable for customer communication.
36 / 45
Slack message:
"@john.doe just reported a 500 error on the `/users/create` endpoint. Users are unable to create new accounts. Initial investigation suggests it might be related to a recent change in the database schema validation logic. We're monitoring."This scenario focuses on communicating an incident effectively. The best response clearly states the problem (500 error on endpoint), acknowledges the potential cause (schema validation change), and confirms ongoing monitoring – all vital elements of a customer-facing update. Options A and C are incorrect because they lack key information, while option D is too technical for a non-technical audience. Option B is partially correct but doesn't fully capture the need to provide context.
37 / 45
PR Description
Subject: Critical Outage - User Account Creation
We experienced a significant outage affecting user account creation today. Users reported encountering a 500 error when attempting to create new accounts. Our initial investigation points towards an issue with the database schema validation, specifically a recent update to the `validate_user_data` function. We've deployed a rollback and are actively monitoring the system. Further updates will follow.
Which of the following best describes the primary purpose of this PR description for a customer-facing communication?This question tests understanding of the core purpose of a customer-facing post-incident summary. While technical details are important internally, the primary goal is to communicate clearly and concisely to users affected by the outage. Option B is incorrect because this description isn't meant for troubleshooting; that's handled through support channels. Option D focuses solely on the development team's actions, neglecting the customer's perspective – a crucial element of effective communication. The correct answer highlights the need to inform customers about the situation and ongoing remediation efforts.
38 / 45
Which of the following options best refines this message for a customer-facing update, focusing on clarity and minimizing alarm?
The original draft is vague and doesn't provide users with enough information to understand the severity of the issue or what they should do in the meantime. Option A correctly identifies this - it's insufficient because it lacks crucial details like impact and timeline. Options B and C are acceptable but don't fully address the need for proactive communication. Option D is too strong, as a 'full fix' isn't guaranteed at this stage.
39 / 45
A customer support team is preparing a summary for users affected by an outage impacting their ability to access key features in a SaaS application. The initial draft reads: "We experienced some issues with the backend services today, which temporarily prevented some users from accessing certain features. Our engineers are working to resolve this." Which of the following options represents the *most* effective revision of this message for direct communication to affected customers, prioritizing clarity and reassurance?
The correct answer (option 0) uses precise language – 'service disruption,' 'identified the cause' – demonstrating professionalism and providing a clear picture of the situation. It avoids vague terms like 'some issues' and offers reassurance about a solution without over-promising. Options B and D are too informal, while option C focuses solely on acknowledging the problem without outlining corrective actions.
40 / 45
A developer is drafting a post-incident summary for a critical outage affecting the API's ability to retrieve user profiles. The initial draft reads: 'Yesterday, we had some performance degradation impacting profile retrieval. We've optimized queries and are monitoring.' Which of the following options best refines this message for a customer-facing update, focusing on transparency and acknowledging impact?
The correct answer emphasizes transparency by acknowledging the *impact* of the degradation (affected retrieval times) and clearly stating what actions were taken (optimizations & monitoring). Options B and D are too dismissive or vague. Option C introduces unnecessary alarm without specific details, while option A provides a balanced and informative update suitable for customer communication.
41 / 45
Slack message:
"@john.doe just reported a 500 error on the `/users/create` endpoint. Users are unable to create new accounts. Initial investigation suggests it might be related to a recent change in the database schema validation logic. We're monitoring."This scenario focuses on communicating an incident effectively. The best response clearly states the problem (500 error on endpoint), acknowledges the potential cause (schema validation change), and confirms ongoing monitoring – all vital elements of a customer-facing update. Options A and C are incorrect because they lack key information, while option D is too technical for a non-technical audience. Option B is partially correct but doesn't fully capture the need to provide context.
42 / 45
PR Description
Subject: Critical Outage - User Account Creation
We experienced a significant outage affecting user account creation today. Users reported encountering a 500 error when attempting to create new accounts. Our initial investigation points towards an issue with the database schema validation, specifically a recent update to the `validate_user_data` function. We've deployed a rollback and are actively monitoring the system. Further updates will follow.
Which of the following best describes the primary purpose of this PR description for a customer-facing communication?This question tests understanding of the core purpose of a customer-facing post-incident summary. While technical details are important internally, the primary goal is to communicate clearly and concisely to users affected by the outage. Option B is incorrect because this description isn't meant for troubleshooting; that's handled through support channels. Option D focuses solely on the development team's actions, neglecting the customer's perspective – a crucial element of effective communication. The correct answer highlights the need to inform customers about the situation and ongoing remediation efforts.
43 / 45
Which of the following options best refines this message for a customer-facing update, focusing on clarity and minimizing alarm?
The original draft is vague and doesn't provide users with enough information to understand the severity of the issue or what they should do in the meantime. Option A correctly identifies this - it's insufficient because it lacks crucial details like impact and timeline. Options B and C are acceptable but don't fully address the need for proactive communication. Option D is too strong, as a 'full fix' isn't guaranteed at this stage.
44 / 45
A customer support team is preparing a summary for users affected by an outage impacting their ability to access key features in a SaaS application. The initial draft reads: "We experienced some issues with the backend services today, which temporarily prevented some users from accessing certain features. Our engineers are working to resolve this." Which of the following options represents the *most* effective revision of this message for direct communication to affected customers, prioritizing clarity and reassurance?
The correct answer (option 0) uses precise language – 'service disruption,' 'identified the cause' – demonstrating professionalism and providing a clear picture of the situation. It avoids vague terms like 'some issues' and offers reassurance about a solution without over-promising. Options B and D are too informal, while option C focuses solely on acknowledging the problem without outlining corrective actions.
45 / 45
A developer is drafting a post-incident summary for a critical outage affecting the API's ability to retrieve user profiles. The initial draft reads: 'Yesterday, we had some performance degradation impacting profile retrieval. We've optimized queries and are monitoring.' Which of the following options best refines this message for a customer-facing update, focusing on transparency and acknowledging impact?
The correct answer emphasizes transparency by acknowledging the *impact* of the degradation (affected retrieval times) and clearly stating what actions were taken (optimizations & monitoring). Options B and D are too dismissive or vague. Option C introduces unnecessary alarm without specific details, while option A provides a balanced and informative update suitable for customer communication.
Frequently Asked Questions
What does the "Customer-Facing Post-Incident Summary — Writing Vocabulary" exercise cover?
Write clear, trustworthy customer-facing post-incident summaries.
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.
How many questions are in "Customer-Facing Post-Incident Summary — Writing Vocabulary"?
This exercise has 45 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more External Crisis Communication exercises?
Browse the full External Crisis Communication hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.