Match rules are so strict that true duplicate customer rows never merge, leaving fragmented service history across systems. What does this situation represent?
Select an answer to reveal the explanation.
Short Explanation
If the twins never get introduced, you still have two half-stories about one customer—that miss is a false negative. Strict rules feel safe until service desks cannot see the whole history. Tune precision and recall to the risk you can live with.
Full Explanation
False negatives fail to link records that represent the same real-world entity, fragmenting history and weakening customer insight. Overly strict match criteria increase that miss rate. Matching design balances precision (avoid wrong merges) and recall (find true duplicates) according to domain risk—not by abandoning MDM or treating fragmentation as a success.