MDM Data Modeling & Master Data Architecture 2 — Questions and Answers
Question 1: In Informatica MDM, what does a 'base object' represent in the hub store?
- A temporary staging table for incoming records
- The consolidated master record that stores the best-version-of-truth data (Correct answer)
- A lookup table for reference data
- A log table capturing all data changes
Correct answer: The consolidated master record that stores the best-version-of-truth data
A base object in Informatica MDM Hub stores the consolidated, trusted master record after match and merge processing.
Question 2: Which concept describes the process of linking related master data entities across different domains in Informatica MDM?
- Survivorship
- Cross-referencing
- Relationship management (Correct answer)
- Hierarchy management
Correct answer: Relationship management
Relationship management in Informatica MDM defines and manages links between entities such as Person-to-Organization or Product-to-Category.
Question 3: What is the purpose of a 'landing table' in the Informatica MDM staging process?
- It stores the final merged master records
- It holds raw source records before they undergo any MDM processing (Correct answer)
- It captures records that failed validation
- It stores cross-reference data between source systems
Correct answer: It holds raw source records before they undergo any MDM processing
Landing tables are the initial destination for raw source data before it is cleansed, standardized, and staged for MDM processing.
Question 4: In an Informatica MDM hub schema, what distinguishes a 'many-to-many' relationship table from a standard base object?
- It stores denormalized data for reporting
- It manages associations between two base objects without creating a new master entity (Correct answer)
- It holds historical versions of merged records
- It contains metadata about system configurations
Correct answer: It manages associations between two base objects without creating a new master entity
A many-to-many relationship table in MDM Hub links two base objects (e.g., Person and Organization) to represent associations without creating a standalone master entity.
Question 5: Which MDM architectural pattern is BEST suited when a single authoritative version of master data must be stored centrally and all consuming systems reference it?
- Registry style
- Coexistence style
- Centralized (Consolidation) style (Correct answer)
- Federated style
Correct answer: Centralized (Consolidation) style
The Centralized or Consolidation style stores the master record in a single hub that all systems treat as the system of record.
Question 6: In Informatica MDM, what is the role of 'trust settings' during survivorship?
- They define which source system's attribute value is most reliable and should be preferred in the golden record (Correct answer)
- They encrypt sensitive attributes in the hub store
- They determine how long a record is retained before archival
- They control user access permissions to base objects
Correct answer: They define which source system's attribute value is most reliable and should be preferred in the golden record
Trust settings assign confidence scores to source systems per attribute, guiding survivorship rules to select the most reliable value for the golden record.
Question 7: What is a 'cross-reference (XREF) table' used for in Informatica MDM Hub?
- To store the canonical master record after consolidation
- To map source system record identifiers to the corresponding hub UID (Correct answer)
- To log all user-initiated manual merges
- To define matching rules between base objects
Correct answer: To map source system record identifiers to the corresponding hub UID
XREF tables maintain the mapping between each source system's record key and the MDM Hub's unique identifier (RowID), enabling lineage tracking.
MDM Data Modeling & Master Data Architecture 2
In Informatica MDM, what does a 'base object' represent in the hub store?