Mixed Scenarios 07–12 — Prompts Only
7 — Valid Status, Rising Defects
The Data Steward has approved Active / Inactive / Pending as valid Customer Status values. After a release, invalid statuses triple. The team debates whether the Steward should define more values or whether someone should diagnose the new failure pattern.
8 — Product Means Something Different in Every Mart
Sales and Inventory both use a Product dimension, but product categories, IDs and descriptions differ. Cross-process analysis produces contradictory results. A BI developer proposes a one-off mapping inside the executive dashboard.
9 — Perfect Format, Wrong Person
An email address passes every format/domain rule and loads successfully into the warehouse, but it actually belongs to another customer. The team wants to add an even stricter regular-expression validator.
10 — Governed Codes vs Warehouse Conversion
Source systems use US, USA, and 840. The organization has not yet decided which representations are accepted or how they map. The warehouse team wants to choose a conversion rule locally so the load can proceed.
11 — Temporary Load Area or Operational Store?
A table holds raw extracts only while records are cleansed and transformed before loading the analytical platform; it is routinely truncated. A separate proposed store would retain integrated near-current data for operational reporting.
12 — Clean the Addresses Again
Every month, the DQ team repairs tens of thousands of bad addresses. The same source workflow allows the defects to return. Leaders propose automating the monthly cleanup because “the correction process works.”