← All MDM Flashcard Decks

Match and Merge Rules Flashcards

7 cards from real MDM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Match and Merge Rules flashcards as text
  1. In Informatica MDM, what is the purpose of a 'fuzzy match' key?

    Answer: To generate phonetic or approximate keys that allow near-duplicate detection

    Fuzzy match keys generate phonetic or approximate representations of data values, enabling MDM to identify near-duplicate records that differ slightly in spelling or format.

  2. Which Informatica MDM component is responsible for executing the match process against a set of records?

    Answer: Match Server (cmxmatch)

    The Match Server (cmxmatch) is a dedicated Informatica MDM component that executes match column analysis and scoring against candidate record sets.

  3. What does the 'Consolidation Indicator' (CONSOLIDATION_IND) on a base object record signify?

    Answer: The merge state of the record — for example, 'R' for merged, 'B' for consolidated

    CONSOLIDATION_IND tracks the merge lifecycle state of a record; values such as 'R' (merged/removed) and 'B' (best-of-breed consolidated) indicate where the record stands in the merge workflow.

  4. In an Informatica MDM match rule set, what is the role of a 'primary match column'?

    Answer: It is the first column evaluated; records must match on it before additional columns are assessed

    A primary match column acts as an initial filter; records that do not satisfy the primary column condition are excluded from further comparison, improving match performance.

  5. When configuring a match rule in Informatica MDM Hub Console, what does the 'Match Column Search Level' property control?

    Answer: How broadly or narrowly MDM searches for candidate records using match keys

    The Match Column Search Level determines the breadth of candidate retrieval — a broader level returns more candidates for comparison, while a narrower level limits the search for efficiency.

  6. What happens when two records exceed the 'Auto-Merge Threshold' in Informatica MDM?

    Answer: They are automatically merged without human intervention

    Records whose match score exceeds the Auto-Merge Threshold are merged automatically by the system, bypassing manual review queues.

  7. In Informatica MDM, which merge style produces a single 'golden record' by applying cell-level trust rules across all contributing source records?

    Answer: Trust-based (best-of-breed) merge

    Trust-based (best-of-breed) merge evaluates trust scores for each cell across all cross-references and selects the highest-trust value for each attribute in the golden record.