After a data integration job, orphan foreign keys spike in a municipal case-management warehouse. What does this primarily indicate?
Select an answer to reveal the explanation.
Short Explanation
When child rows show up without parents after a load, the integration just broke the family tree. Mapping and sequencing mistakes are common DQ failure modes in ETL/ELT. Treat the spike as an integration defect, not a random coincidence.
Full Explanation
Data integration can create referential breaks when mappings, keys, or load order are wrong. A spike in orphan foreign keys after a job is a classic integration-induced DQ failure. Ensuring DQ in integration includes validating relationships, not only row counts.