MDM Staging and Loading 5 — Questions and Answers
Question 1: In Informatica MDM, which log or table should an administrator first consult to diagnose why records are not appearing in the base object after a load job completes?
- The match analysis report
- The reject/error table and batch job log (Correct answer)
- The XREF table audit trail
- The trust configuration history
Correct answer: The reject/error table and batch job log
The reject/error table captures records that failed validation or constraint checks, and the batch job log records execution details and error messages, making them the first diagnostic resources.
Question 2: When an Informatica MDM batch group is configured with a 'Stage and Load' job sequence, what is the risk of running multiple batch groups concurrently against the same base object?
- Duplicate XREF entries can be created, causing orphaned cross-references
- Trust scores are recalculated globally, resetting all prior survivorship decisions
- Delta detection results can conflict, leading to missed or duplicated record processing (Correct answer)
- The match threshold is automatically lowered to compensate for increased data volume
Correct answer: Delta detection results can conflict, leading to missed or duplicated record processing
Running concurrent stage/load jobs against the same base object can cause race conditions where delta detection windows overlap, resulting in records being skipped or processed twice.
Question 3: Which Informatica MDM concept describes the process of writing source record attribute values into the XREF table rather than directly overwriting the base object during load?
- Survivorship
- Cross-referencing (Correct answer)
- Tokenization
- Consolidation indicator
Correct answer: Cross-referencing
Cross-referencing stores each source system's attribute values in the XREF table, preserving the original source data while allowing survivorship rules to compute the base object's best value.
Question 4: In Informatica MDM, what does the term 'initial load' specifically refer to in the context of staging and loading?
- The first incremental load after a system outage
- The first-time full population of the hub from all source systems (Correct answer)
- Loading only the highest-priority source system before others are onboarded
- A test load using synthetic data to validate mappings
Correct answer: The first-time full population of the hub from all source systems
An initial load is the first end-to-end full load of all source data into a newly configured MDM hub, establishing the baseline set of records from which incremental loads continue.
Question 5: Which Informatica MDM Hub component is responsible for executing the stage and load batch jobs on a schedule?
- IDD (Informatica Data Director)
- Hub Server with batch framework / ORS batch API (Correct answer)
- Data Integration Service (DIS)
- Metadata Manager Service
Correct answer: Hub Server with batch framework / ORS batch API
The MDM Hub Server exposes a batch framework (ORS batch API) that executes stage, load, match, and merge jobs, either on demand or via external schedulers.
Question 6: When configuring mappings for a landing table to staging table transition in Informatica MDM, which field mapping is mandatory to enable proper delta detection?
- PKEY_SRC_OBJECT (source primary key) (Correct answer)
- ROWID_OBJECT (MDM surrogate key)
- HUB_STATE_IND (processing state)
- CONSOLIDATION_IND (merge status)
Correct answer: PKEY_SRC_OBJECT (source primary key)
PKEY_SRC_OBJECT must be mapped because it carries the source system's primary key, which MDM uses during delta detection to compare incoming records against previously staged data.
Question 7: In Informatica MDM, what is the purpose of the 'Tokenize' job that sometimes precedes the match job in a batch group sequence?
- It compresses staging records to save database storage
- It generates match tokens from key fields to enable efficient fuzzy matching (Correct answer)
- It encrypts sensitive PII fields before they are written to the base object
- It converts XML source data into relational staging table format
Correct answer: It generates match tokens from key fields to enable efficient fuzzy matching
The Tokenize job pre-computes match tokens (standardized, phonetic, or algorithmic representations) from key attributes, which the match engine then uses to efficiently find candidate duplicate pairs.
MDM Staging and Loading 5
In Informatica MDM, which log or table should an administrator first consult to diagnose why records are not appearing in the base object after a load job completes?