MDM Hub Configuration and Management 5 — Questions and Answers
Question 1: In Informatica MDM Hub, what does SIF stand for and what is its primary role?
- Services Integration Framework — provides an API for external applications to read and write MDM Hub data (Correct answer)
- Schema Integration Foundation — manages base object schema versioning
- Source Ingestion Framework — automates landing table loading from source systems
- Security Integration Facility — handles SSO authentication for Hub Console
Correct answer: Services Integration Framework — provides an API for external applications to read and write MDM Hub data
SIF (Services Integration Framework) exposes MDM Hub operations as web services, allowing external applications to query golden records, trigger merges, and update data programmatically.
Question 2: Which MDM Hub feature allows administrators to track how a golden record's field values have changed over time?
- Timeline Manager (Correct answer)
- History Viewer
- Audit Manager
- Cross-Reference History log
Correct answer: Timeline Manager
Timeline Manager provides a temporal view of golden record changes, showing which source contributed which value at each point in time.
Question 3: What is the purpose of the 'Hierarchy Manager' in Informatica MDM Hub?
- To define and manage relationships between base object records, such as parent-child or many-to-many associations (Correct answer)
- To control the priority order of match rule sets during the matching process
- To organize source systems into tiers based on their trust score configuration
- To set up the folder hierarchy for Hub configuration exports
Correct answer: To define and manage relationships between base object records, such as parent-child or many-to-many associations
Hierarchy Manager lets MDM administrators model and visualize complex entity relationships—like organization charts or product hierarchies—on top of the consolidated golden records.
Question 4: In MDM Hub, what happens during an 'unmerge' operation?
- Previously merged cross-reference records are separated and each becomes its own independent golden record (Correct answer)
- A golden record is rolled back to an earlier version using timeline data
- A source system's data contribution is removed from the BVT calculation permanently
- The match tokens for a base object are deleted and regenerated from scratch
Correct answer: Previously merged cross-reference records are separated and each becomes its own independent golden record
An unmerge splits a consolidated golden record back into its constituent source records, each of which re-enters the match queue for potential re-consolidation.
Question 5: Which Informatica MDM Hub deployment artifact contains the entire Hub configuration—including base objects, match rules, and mappings—and is used for environment promotion?
- Hub Configuration Export (HCI) package (Correct answer)
- Hub Resource Kit archive
- Process Server deployment bundle
- SIF WSDL descriptor
Correct answer: Hub Configuration Export (HCI) package
An HCI (Hub Configuration Import/Export) package captures the full MDM Hub metadata configuration, enabling migration of settings from development to production without manual reconfiguration.
Question 6: When a source system is configured in MDM Hub as a 'trust-only' source, what does this mean?
- The source can contribute field values to the BVT calculation but cannot add new records to the base object (Correct answer)
- The source is trusted unconditionally and its records bypass match processing entirely
- The source's records are automatically merged with existing golden records without a match score check
- The source contributes records only when no other source has provided data for that golden record
Correct answer: The source can contribute field values to the BVT calculation but cannot add new records to the base object
A trust-only source participates in survivorship to influence which field values appear in the golden record, but it cannot independently create new golden records.
Question 7: What is the role of the 'delta detection' feature in MDM Hub's staging process?
- It identifies and processes only records that have changed since the last load, reducing processing overhead (Correct answer)
- It detects mismatches between landing and staging column mappings before data is processed
- It compares match scores between successive job runs to flag configuration drift
- It measures the difference in trust scores between two competing source systems
Correct answer: It identifies and processes only records that have changed since the last load, reducing processing overhead
Delta detection compares incoming landing records against previously staged data and skips unchanged records, significantly improving incremental load performance.
MDM Hub Configuration and Management 5
In Informatica MDM Hub, what does SIF stand for and what is its primary role?