Staging and Loading Flashcards
7 cards from real MDM practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 Staging and Loading flashcards as text
During the delta detection phase in Informatica MDM staging, what is the primary purpose of comparing incoming records against the staging table?
Answer: To identify new, updated, or unchanged records from the source
Delta detection compares incoming source records to already-staged data to classify each record as new, changed, or unchanged, reducing unnecessary processing.
Which Informatica MDM staging table stores the raw source data before any cleansing or standardization is applied?
Answer: _STG table
The _STG (staging) table holds the raw inbound source records exactly as they arrive, prior to any transformation or cleanse processing.
In Informatica MDM, what happens to a source record that fails validation during the stage job?
Answer: It is written to the error table and excluded from further processing
Records failing stage validation are routed to the error/reject table, keeping bad data out of the hub while providing an audit trail for remediation.
Which load type in Informatica MDM replaces all existing hub records with incoming source data, regardless of changes?
Answer: Full load
A full load truncates or overwrites existing data and reloads everything from the source, useful for initial loads or complete refreshes.
What is the role of the ROWID_OBJECT column that Informatica MDM assigns during the load process?
Answer: It is the unique surrogate key MDM generates for each base object record
ROWID_OBJECT is the MDM-generated surrogate key that uniquely identifies each record in the base object table, independent of any source system key.
When configuring a batch group in Informatica MDM, which job must typically run BEFORE the load job to ensure data is ready?
Answer: Stage job
The stage job must run first to populate the staging tables from source data before the load job can move records into the base object.
In Informatica MDM Hub, the XREF table created during load primarily serves which purpose?
Answer: Maps source system keys to MDM surrogate keys for cross-referencing
The XREF (cross-reference) table links each source system's native key to the corresponding MDM ROWID_OBJECT, enabling traceability back to originating systems.