MDM Data Integration & Synchronization Techniques 3 — Questions and Answers
Question 1: In Informatica MDM Hub, what distinguishes a 'base object' from a 'staging table'?
- A base object stores raw source data while a staging table stores golden records
- A base object stores the consolidated master records while a staging table holds pre-processed source data (Correct answer)
- A base object is used only for hierarchy data while a staging table handles transactional data
- A base object is read-only while a staging table allows bulk updates
Correct answer: A base object stores the consolidated master records while a staging table holds pre-processed source data
Base objects in MDM Hub contain the consolidated golden records, while staging tables hold raw source data that has been loaded but not yet merged.
Question 2: Which Informatica MDM batch job must be executed to promote staged records through match, merge, and consolidation?
- Publish job
- Load job
- Consolidate job (Correct answer)
- Tokenize job
Correct answer: Consolidate job
The Consolidate (or Match and Merge) batch job processes staged records through match rules, identifies duplicates, and merges them into golden records.
Question 3: When configuring a source system integration in Informatica MDM, what does 'rowid_object' represent?
- The primary key assigned by the source system to each record
- The MDM Hub's internal unique identifier for each base object record (Correct answer)
- The sequence number used to order batch loads
- The hash value generated during the tokenization process
Correct answer: The MDM Hub's internal unique identifier for each base object record
ROWID_OBJECT is the MDM Hub's system-generated unique identifier for each record in a base object, used internally for cross-referencing and relationship management.
Question 4: What is the purpose of the cross-reference (XREF) table in Informatica MDM?
- Mapping match tokens to their source records for efficient lookup
- Tracking which source system records contributed to each golden record (Correct answer)
- Storing the historical versions of golden records before merge
- Defining the column-level mappings between staging and base object tables
Correct answer: Tracking which source system records contributed to each golden record
The XREF table maintains the relationship between each golden record and the individual source system records that were merged to create it, enabling lineage and un-merge operations.
Question 5: An MDM architect needs to integrate a real-time POS system that sends individual transaction records every second. Which integration approach is most appropriate?
- Nightly batch file load via PowerCenter ETL
- SIF (Services Integration Framework) API calls for real-time record processing (Correct answer)
- Manual CSV import through the Hub Console
- Scheduled polling of the POS database every hour
Correct answer: SIF (Services Integration Framework) API calls for real-time record processing
The Services Integration Framework (SIF) API enables real-time, record-by-record integration suitable for high-frequency transaction sources like POS systems.
Question 6: Which process in Informatica MDM ensures that updated golden records are automatically reflected in subscribing applications without requiring those applications to query the Hub?
- Tokenization
- Publication (Correct answer)
- Validation
- Profiling
Correct answer: Publication
The Publication process pushes updated golden records to downstream subscribers via message queues or services, implementing event-driven synchronization.
Question 7: In MDM Hub's data integration, what is the significance of the 'hub state indicator' (HUB_STATE_IND) column on a base object record?
- It records whether a record was loaded via batch or real-time API
- It indicates the consolidation state of the record, such as pending merge or active golden record (Correct answer)
- It flags whether the record passed or failed validation checks
- It stores the geographic region code of the source system that provided the record
Correct answer: It indicates the consolidation state of the record, such as pending merge or active golden record
HUB_STATE_IND tracks the processing state of a record within the MDM Hub, indicating whether it is active, pending consolidation, or in another workflow state.
MDM Data Integration & Synchronization Techniques 3
In Informatica MDM Hub, what distinguishes a 'base object' from a 'staging table'?