Your question is Design a Quality-Gated Visualization Pipeline. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You are building a visualization workflow for a product analytics team that publishes dashboards to internal users and customer-facing reports. The pipeline pulls from operational databases, event streams, and warehouse tables, then feeds curated datasets into the visualization layer. The main problem is that bad upstream data, missing fields, duplicate rows, and late-arriving records can reach end users before anyone notices.
How would you design a visualization workflow that keeps data quality issues from reaching end users?