The short answer
Root-cause analysis finds the underlying reason a quality incident happened, not only the symptom ("dashboard revenue is wrong"). Good RCA prevents repeat failures.
A practical DE workflow
- 1Detect: alert on freshness, volume, test failure, or stakeholder report.
- 2Contain: pause publish / mark asset unhealthy / communicate stale-but-safe status.
- 3Scope blast radius: use lineage: which marts, dashboards, and jobs are affected?
- 4Localize the first bad hop: source empty? ? bad join? late ? wrong filter in yesterday's deploy?
- 5Confirm with evidence: reconciliations, diffs, git/deploy timeline, raw vs staging vs mart samples.
- 6Fix + : correct logic or upstream, reprocess impacted partitions idempotently.
- 7Prevent: add a test/monitor/contract that would have caught this earlier; write a short postmortem.
Symptom: revenue_dashboard -30%
Lineage: dashboard <- fct_orders <- stg_orders <- raw.orders
Finding: raw.orders partition missing for Asia region after producer deploy
Fix: restore producer feed, backfill partition, add source freshness + row-count anomaly gateInterview tip: Emphasize contain → lineage → first bad hop → evidence → backfill → preventive test. RCA is a process, not a guess.