# A daily revenue pipeline has no orchestrator-level SLA; the freshness commitment lives only in a run

Canonical URL: <https://datadriven.io/problems/a-daily-revenue-pipeline-has-no-orchestrator-level-sla-the-4316f707>

Domain: Pipeline Design · Difficulty: medium

## Problem

A daily revenue pipeline has no orchestrator-level SLA; the freshness commitment lives only in a runbook. When the pipeline misses 6am, the on-call notices late. Apply the SLA-at-seam framing this section just taught and declare the SLA structurally. Add an observability_tool node (Monte Carlo, Bigeye, Anomalo, or Datadog) that monitors mart.daily_revenue's freshness, and an alert_destination node (PagerDuty, OpsGenie, Slack, email, or SES) that routes SLA misses to on-call. The observability_tool defines the SLA threshold; the alert_destination is where misses are paged. Together they make the SLA a live, monitored commitment instead of a runbook entry.

## Related

- [All practice problems](https://datadriven.io/problems)
- [Mock interview mode](https://datadriven.io/interview/a-daily-revenue-pipeline-has-no-orchestrator-level-sla-the-4316f707)
- [System Design Interview Questions](https://datadriven.io/data-engineering-system-design)
- [Data Engineering Interview Prep Guide](https://datadriven.io/data-engineer-interview-prep)
- [Daily Challenge](https://datadriven.io/daily)

---

Source: DataDriven (https://datadriven.io). 100% free data engineering interview prep. Live code execution against Postgres 16, Python 3.11, and Spark sandboxes. No paywall, no premium tier, no signup gate.