โ† 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 the 'Segment Match' option in a match rule set?

    Answer: To restrict matching so that records are only compared against others within the same segment (partition) value

    Segment Match limits comparisons to records sharing the same segment column value, reducing false positives and improving performance by partitioning the match space.

  2. Which Informatica MDM batch job must be run before the 'Match' job to ensure match key tables are populated?

    Answer: Tokenize

    The Tokenize batch job must run first to generate and store match key tokens in the match token tables (_MTT); the Match job then uses those tokens to retrieve candidates.

  3. In Informatica MDM trust configuration, what does 'Downgrade Trust on Null' do?

    Answer: It reduces the effective trust score of a source system cell when the incoming update contains a null value

    Downgrade Trust on Null lowers the effective trust score of an update that delivers a null value, helping ensure existing non-null golden record values are not overwritten by null updates from lower-quality sources.

  4. What is the significance of the 'HUB_STATE_IND' column on a base object record in Informatica MDM?

    Answer: It tracks whether the record is active, pending delete, or has been logically deleted

    HUB_STATE_IND indicates the lifecycle state of a base object record: 1 = active, 0 = pending delete, -1 = logically deleted (soft delete).

  5. When configuring an Informatica MDM merge rule, what does 'Last Updated' survivorship strategy mean?

    Answer: The golden record is always populated from the source system with the most recent record update timestamp

    The Last Updated survivorship strategy selects the cell value from the cross-reference record that was most recently updated, regardless of which source system it came from.

  6. In Informatica MDM, what is the role of the 'Merge Manager' (part of the Data Stewardship Portal)?

    Answer: It provides a UI for data stewards to review potential duplicates and approve or reject manual merges

    Merge Manager is the Data Stewardship Portal screen where data stewards review candidate duplicate record pairs surfaced by the match process and decide whether to merge or unlink them.

  7. What happens to the ROWID_OBJECT of the surviving golden record after two records are merged in Informatica MDM?

    Answer: The ROWID_OBJECT of the record designated as the merge survivor is retained; the other record's ROWID becomes its cross-reference identifier

    During merge, one record is designated the survivor and retains its ROWID_OBJECT as the golden record's identifier; the other record's ROWID is preserved in the _XREF table as a cross-reference.