Scenario: A schema change breaks downstream reports. What reduces blast radius?
evolutionScenario: Pipelines run but outputs degrade silently. What do you add?
monitoringScenario: You must choose quality checks. What makes a check 'good'?
qualityScenario: You need to prove lineage for an audit. What evidence do you keep?
lineageScenario: Teams keep rebuilding the same transformations. What is the best architectural response?
operating-modelScenario: You need to backfill historical data after a bug. What is the main risk?
evolutionA freshness SLO for a dataset is most defensibly defined as:
monitoringScenario: A check fails. What makes the response credible?
qualityScenario: A dataset is correct but arrives too late for decisions. What should you add?
monitoringScenario: A column is renamed and downstream breaks. What design practice prevents this?
evolutionScenario: A privacy incident occurs. What helps you scope impact quickly?
lineageScenario: Central team is overloaded. What is the most defensible scaling move?
operating-model