An initial MDM load floods the match queue with years of historical duplicates. What should the implementation plan include?
Select an answer to reveal the explanation.
Short Explanation
First loads dump a mountain of suspects on the desk. Plan the backlog and prioritize what matters—don’t auto-merge everything or throw history away.
Full Explanation
Initial loads commonly create large match-queue backlogs. Programs need prioritized stewardship, sampling, and rules for high-impact entities rather than blind auto-merge, indefinite dual-keying freezes, or deleting historical sources.