1 / 5
Scenario: "The data team needs to define SLOs for the customer events table." What is the difference between SLI, SLO, and SLA in a data context?
-
-
-
-
SLI/SLO/SLA hierarchy: SLI (measurement) → SLO (internal goal) → SLA (external commitment with legal/financial consequence for breach).
Key vocab: SLI, SLO, SLA, error budget, breach remediation.
2 / 5
Scenario: "The data SLA was breached." What does this typically trigger?
-
-
-
-
SLA breach process: alert → notify consumers → investigate → remediate → PIR. Contract should define: SLA metrics, breach definition, notification SLA (e.g., notify consumers within 30 min of breach detection), remediation target.
Key vocab: SLA breach, breach notification, remediation SLA, incident log, PIR (Post-Incident Review).
3 / 5
Scenario: "The contract includes a grace period for freshness." What is a grace period in data SLA terms?
-
-
-
-
Grace period: "official breach = SLA + grace". Prevents alert fatigue from minor threshold crossings. Tune carefully — too long hides real issues.
Key vocab: grace period, breach threshold vs. official breach, alert suppression window, SLA tolerance.
4 / 5
Scenario: "The analytics team wants to set a p99 freshness SLO." What does p99 mean in this context?
-
-
-
-
Percentile SLOs: "p99 freshness < 4h" means 99% of hourly measurements show data less than 4h old. Error budget = 1% = ~3.65 days/year.
Key vocab: p99 SLO, percentile threshold, error budget calculation, error budget spend.
5 / 5
Scenario: "The team is escalating a freshness SLA breach." What vocabulary is used in a standard data incident escalation?
-
-
-
-
Incident declaration structure: severity (P1/P2) + affected asset + metric value vs. SLA threshold + impact scope + escalation path. Professional escalation = no blame, clear facts, actionable.
Key vocab: data incident declaration, SLA breach communication, impact scope, escalation path, on-call escalation.