Mixed Scenarios 01–06 — Prompts Only
For each scenario, write all seven decision layers before opening the resolution key.
1 — Three Revenue Numbers
Sales, Finance and the executive dashboard each use a different definition of Net Revenue. The warehouse team can change SQL, but nobody has authority to say which definition is official. Executives want “the dashboard fixed by Friday.”
2 — One Customer, Three IDs, Two Country Codes
A customer acquired through a merger appears under three local IDs across CRM and billing. The same sources also represent the United States as US, USA, and 840. The business asks for “one clean Customer.”
3 — Merger Blueprint vs Project Schema
After an acquisition, leadership needs an enterprise target for Customer, Product and Location that all future projects should reuse. At the same time, one project team is arguing over Customer–Order cardinality, keys and normalization.
4 — The ETL Fixes It Every Night
A source application repeatedly produces malformed customer-status values. The warehouse ETL converts them into valid-looking target values every night, so reports look clean. The same defects keep appearing upstream and nobody changes the source process.
5 — We Found the Table, But What Does It Mean?
A catalog search reveals the table and system containing cust_st. Analysts still do not know what the field means, which values are valid, or its datatype/nullability. Several teams assume the catalog entry itself should answer everything.
6 — Current Data vs Historical Record
Operations wants an integrated store refreshed every few minutes for near-current reporting. Audit also requires reproducible five-year history. A design proposal labels one volatile 30-day store “the enterprise warehouse” and assumes it satisfies both needs.