MDM Architecture and Datamodel 4 — Questions and Answers
Question 1: In MDM Hub, what is the function of the 'Merge Manager' tool?
- Automates the batch merge of all matched record pairs without human review
- Provides a data steward interface to review match results and approve or reject proposed merges (Correct answer)
- Configures the trust and survivorship rules for field-level consolidation
- Exports merged golden records to downstream systems
Correct answer: Provides a data steward interface to review match results and approve or reject proposed merges
Merge Manager is a data stewardship tool that allows stewards to review pending match pairs and manually approve merges, reject false matches, or unmerge previously merged records.
Question 2: Which MDM Hub configuration determines the minimum match score required for two records to be automatically merged without human review?
- Auto-merge threshold in the Match Rule Set (Correct answer)
- Trust decay factor in the source system configuration
- Consolidation indicator threshold in the base object
- Minimum confidence score in the cleanse function
Correct answer: Auto-merge threshold in the Match Rule Set
The auto-merge threshold, set within a Match Rule Set, specifies the minimum match score above which records are automatically merged without requiring data steward review.
Question 3: What is the purpose of 'Hierarchy Manager' in Informatica MDM Hub?
- To manage the version history of schema changes in the ORS
- To define, store, and query parent-child hierarchical relationships between master records (Correct answer)
- To organize match rule sets into processing hierarchies
- To control the priority hierarchy of source systems for survivorship
Correct answer: To define, store, and query parent-child hierarchical relationships between master records
Hierarchy Manager enables the definition, storage, and querying of hierarchical relationships (such as organizational charts or product categories) between master data records.
Question 4: In MDM Hub's trust-based survivorship, what does 'trust decay' mean?
- The gradual reduction of a source record's trust score over time if not refreshed (Correct answer)
- The decrease in match confidence when records have missing fields
- The reduction in a source system's priority ranking due to data quality failures
- The expiration of cross-reference records after a configurable period
Correct answer: The gradual reduction of a source record's trust score over time if not refreshed
Trust decay is a configurable feature in MDM Hub that reduces a source record's trust score over time unless the source sends an updated value, reflecting data staleness.
Question 5: Which component of the MDM Hub architecture stores the configuration metadata such as match rules, trust settings, and cleanse function definitions?
- The landing tables within each ORS
- The CMX_SYSTEM schema (Hub Store repository) (Correct answer)
- The Process Server cache
- The SIF API configuration files
Correct answer: The CMX_SYSTEM schema (Hub Store repository)
The CMX_SYSTEM schema is the central metadata repository that stores all hub configuration including match rules, source system definitions, trust settings, and cleanse mappings.
Question 6: In Informatica MDM Hub, what is a 'Fuzzy Match' as opposed to an 'Exact Match'?
- Fuzzy match compares encrypted tokens while exact match compares plain text
- Fuzzy match allows for variations and similarities in values, while exact match requires character-for-character equality (Correct answer)
- Fuzzy match operates on numeric fields while exact match operates on text fields
- Fuzzy match is a manual steward decision while exact match is automated
Correct answer: Fuzzy match allows for variations and similarities in values, while exact match requires character-for-character equality
Fuzzy matching uses algorithms to identify records with similar but not identical values (e.g., 'John Smith' vs 'Jon Smyth'), while exact matching requires values to be character-for-character identical.
Question 7: What does the 'LAST_UPDATE_DATE' system column track in an MDM Hub base object record?
- The date the record was first loaded from the source system
- The date the golden record was last modified by any consolidation or stewardship action (Correct answer)
- The date the source system last verified the record's accuracy
- The scheduled date for the next trust decay recalculation
Correct answer: The date the golden record was last modified by any consolidation or stewardship action
LAST_UPDATE_DATE records the most recent timestamp at which the golden record in the base object was modified, whether through batch consolidation or manual data stewardship.
MDM Architecture and Datamodel 4
In MDM Hub, what is the function of the 'Merge Manager' tool?