An alert fires: "The data pipeline SLA was breached — the reporting dataset was delayed by 4 hours."
Which stakeholders must be notified first in a data SLA breach?
SLA breach communication — who needs to know and when:
Notification priority
Audience
Why urgent
Immediate
Dependent business consumers + eng leadership
They may be acting on stale data right now
During incident
Regular updates to affected teams
Manage expectations, allow workaround
Post-resolution
All-clear notification + RCA summary
Data is safe to use again
Message template: what data is affected, issue time, estimated recovery, business impact, any available workaround. Key vocabulary: SLA breach notification, business impact assessment, interim workaround, recovery ETA, impacted stakeholders.
2 / 14
During an incident, the team announces: "We are investigating an ingestion failure affecting the events table — data from the last 6 hours may be incomplete. Please treat any reports from that window as preliminary."
What communication principle does this statement follow?
Data incident communication best practices:
Principle
Action in the example
Acknowledge early
"We are investigating" — before root cause known
Define affected scope
Specific table + 6-hour time window named
Warn consumers
"Treat reports as preliminary"
Never wait for root cause before communicating impact to consumers. Key vocabulary: data incident, impacted time window, preliminary data warning, update cadence, data incident runbook.
3 / 14
A post-incident RCA states: "A schema change caused a silent data drop — the pipeline succeeded but records were missing."
What does "silent data drop" mean in a data pipeline context?
Silent data drop — one of the hardest data incidents to detect:
Type
What happened
Detection method
Silent drop
Pipeline exit code 0, but rows are missing
Row count monitoring, reconciliation
Explicit failure
Error raised, pipeline stopped
Error alerts, monitoring dashboards
Common causes: new NOT NULL column rejected rows silently, schema mismatch filtering, API pagination bug. Key vocabulary: silent failure, data loss without error, quality check gate, expected vs. actual row count check.
4 / 14
An incident resolution message reads: "The data team will perform a backfill for the affected date range."
What does a backfill involve in data engineering?
Backfill = run pipeline for past time periods to fill gaps or correct errors:
Backfill concept
Explanation
Idempotent backfill
Re-running produces the same result (uses WRITE_TRUNCATE or UPSERT)
Backfill window
The date range being re-processed
Incremental backfill
Re-process day by day to control cost/load
Key vocabulary: backfill window, idempotent backfill, backfill schedule, incremental backfill, cost of full historical backfill.
5 / 14
A post-mortem action item reads: "Add a row count check gate that fails the pipeline if ingested rows differ from expected by more than 5%."
What type of data reliability improvement does this represent?
Data observability = monitoring data health in production:
Observability pillar
What it monitors
Freshness
Is data up-to-date?
Volume
Is row count within expected range? (this action)
Schema
Did column names/types change unexpectedly?
Distribution
Are value distributions normal?
This action adds a volume anomaly detection gate. Key vocabulary: data observability, quality gate, row count SLO, anomaly detection threshold, shift-left data quality.
6 / 14
You're a DevOps engineer and receive the following Slack message from your data team:
'Urgent: We've detected a potential issue with the customer transaction data. The API endpoint returns a 500 error intermittently, and we're seeing increased latency in queries against that table. Initial investigation suggests it might be related to recent schema changes.'
Which of the following is the MOST appropriate immediate response to this message, considering your role and responsibilities?
The correct response acknowledges the issue and requests further information to understand the scope and potential impact. The other options are insufficient because they don't actively participate in assessing the situation or directing the investigation. Asking about schema changes is crucial as these often trigger unexpected data behavior, and understanding the current status allows for timely escalation if needed. It's important to shift from passive observation to active engagement in a critical incident.
7 / 14
You're a DevOps engineer and receive the following Slack message from your data team:
'Urgent: We've detected a potential issue with the customer transaction data. The API endpoint returns a 500 error intermittently, and we're seeing increased latency in queries against that table. Initial investigation suggests it might be related to recent schema changes.'
Which of the following is the MOST appropriate immediate response to this message, considering your role and responsibilities?
The correct response acknowledges the issue and requests further information to understand the scope and potential impact. The other options are insufficient because they don't actively participate in assessing the situation or directing the investigation. Asking about schema changes is crucial as these often trigger unexpected data behavior, and understanding the current status allows for timely escalation if needed. It's important to shift from passive observation to active engagement in a critical incident.
8 / 14
You're a DevOps engineer and receive the following Slack message from your data team:
'Urgent: We've detected a potential issue with the customer transaction data. The API endpoint returns a 500 error intermittently, and we're seeing increased latency in queries against that table. Initial investigation suggests it might be related to recent schema changes.'
Which of the following is the MOST appropriate immediate response to this message, considering your role and responsibilities?
The correct response acknowledges the issue and requests further information to understand the scope and potential impact. The other options are insufficient because they don't actively participate in assessing the situation or directing the investigation. Asking about schema changes is crucial as these often trigger unexpected data behavior, and understanding the current status allows for timely escalation if needed. It's important to shift from passive observation to active engagement in a critical incident.
9 / 14
You're a DevOps engineer and receive the following Slack message from your data team:
'Urgent: We've detected a potential issue with the customer transaction data. The API endpoint returns a 500 error intermittently, and we're seeing increased latency in queries against that table. Initial investigation suggests it might be related to recent schema changes.'
Which of the following is the MOST appropriate immediate response to this message, considering your role and responsibilities?
The correct response acknowledges the issue and requests further information to understand the scope and potential impact. The other options are insufficient because they don't actively participate in assessing the situation or directing the investigation. Asking about schema changes is crucial as these often trigger unexpected data behavior, and understanding the current status allows for timely escalation if needed. It's important to shift from passive observation to active engagement in a critical incident.
10 / 14
During an incident investigation, the monitoring system alerts you to a sudden spike in HTTP 503 errors originating from your customer-facing API. Initial analysis suggests a potential resource exhaustion issue. Which of the following actions should be prioritized first?
The primary goal is to understand *why* the errors are occurring before taking drastic action. A 503 error often indicates resource limits – investigating traffic patterns or bot activity will help determine if this is a legitimate issue or a symptom of a larger problem. Rollbacks should be reserved for later stages after understanding the cause.
11 / 14
You're reviewing a code change that adds logging to a critical data transformation process. The developer has added `console.log()` statements throughout the function but hasn't included any filtering or sanitization of the log output. What is the MOST important concern you should raise during the review?
While documentation and testing are important, the immediate risk is data leakage. Unsanitized logs can expose sensitive information – this is a critical security concern. Focusing on log filtering/sanitization should be the top priority in this review.
12 / 14
A colleague sends you this Slack message: 'Our nightly data sync failed again – we're seeing a lot of 'connection refused' errors. The logs show the database server is unreachable.' What's your *immediate* response to this message?
The message highlights a specific error and potential cause. A productive response involves confirming the issue, requesting more information (logs), and initiating an investigation. Simply stating a generic solution or dismissing the problem isn't helpful.
13 / 14
You're drafting the PR description for a change that updates the schema of a large data warehouse table. The description includes the following sentence: 'This update will improve query performance.' What additional information should you *definitely* include in the PR description to ensure transparency and facilitate rollback if needed?
Simply stating that the change improves performance is insufficient. Quantifying the improvement (if possible), outlining the rollback strategy, and detailing the validation steps are crucial for accountability and risk mitigation during a schema update – especially in large data warehouses.
14 / 14
During your daily stand-up, you report: 'I'm currently working on implementing a new automated retry mechanism for failed API calls to our third-party data provider. The goal is to improve the resilience of our data ingestion pipeline.' Which aspect of this update is MOST important to highlight to the team?
While technical details are relevant, the core focus during a stand-up is communicating the *impact* of your work. Highlighting potential latency implications ensures everyone understands the trade-offs and that it doesn't negatively affect other services.
What does the "Data Incident Communication" exercise practise?
Practice English for data incident communication: SLA breach notifications, silent data drops, backfills, and data observability vocabulary for data engineers.
How many questions are in this exercise?
This exercise has 14 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Data Engineering Language category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Data Incident Communication" part of a larger series?
Yes — it's one exercise in the Data Engineering Language category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Data Engineering Language category page for related exercises, or browse the main Exercises hub for other IT English topics.