Fraud and audit teams need prior resident addresses after a move updates the golden record. What MDM design requirement should be included?
Select an answer to reveal the explanation.
Short Explanation
A golden record that forgets last year's address is a goldfish—shiny, but useless for fraud trails. Keep the history of what changed and when. Auditors need yesterday's porch as much as today's.
Full Explanation
Fraud and audit teams that need prior resident addresses after a move updates the golden record require MDM design that preserves temporal history of master attribute changes when audit and operations need prior values. Civic investigations cannot accept silent overwrite of history. Overwriting history so only the newest address ever exists fails audit and fraud use cases. Storing prior addresses only in email archives outside governed MDM fails chain-of-custody and findability. Forbidding address changes because history retention conflicts with golden-record principles fails; golden records can be current while history is retained. Exam caveat: temporal master history (as-of / effective dating) is a recognized MDM design requirement when audit needs prior values. Operational check: implement effective-dated address history, verify auditors can retrieve prior values, and restrict who can purge history. Align retention of historical master attributes with municipal records schedules and legal holds. Keep verification evidence with the municipal runbook so audits can prove the chosen control was applied as designed and that rejected alternatives would have left city services exposed to the failure modes described above.