Marlow’s billing database is a Postgres owned by the payments team: 4.2 million orders, updated all day, and rows are genuinely deleted. Analysts and a customer-support tool need the warehouse within five minutes, including the orders that disappear. Design the pipeline that reads changes rather than rows.
Five minutes is a deadline, not a cadence. Say what makes work happen and how you would know it had stopped.
Practice studio
Run the review to check your architecture against this scenario — a valid DAG, a trigger for the freshness SLA, a transform stage, a quality gate before publish, and a failure path — then defend it in a short interview.
This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.