Survivorship must keep the oldest account-open date but the newest verified email when records merge. What rule design is required?
Select an answer to reveal the explanation.
Short Explanation
One merge rule doesn’t fit every field. Keep the oldest open date, the newest good email—survivorship can be composite by attribute.
Full Explanation
Survivorship that must keep the oldest account-open date but the newest verified email requires composite survivorship with different strategies per attribute—such as oldest date versus newest trusted email. One global rule rarely fits all civic attributes. One global rule that always keeps the entire losing record verbatim fails attribute-level needs. Random attribute picks with no documented strategy fail auditability. Always discarding dates and emails so the golden record stays empty fails fitness-for-use. Exam caveat: composite / per-attribute survivorship strategies are standard MDM design. Operational check: specify strategy per critical attribute, test merges for date-versus-email behavior, and log winning sources. Approve the composite matrix with domain stewards in the municipal MDM design authority. 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. 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.