MDM Staging and Loading 4 — Questions and Answers
Question 1: When configuring a source system in Informatica MDM Hub Console, which setting determines the default trust level assigned to records from that source during load?
- Cleanse function mapping
- Source system trust settings (Correct answer)
- Landing table schema definition
- Batch group execution order
Correct answer: Source system trust settings
Trust settings defined per source system establish the baseline confidence score MDM assigns to each attribute from that source, influencing survivorship decisions during load.
Question 2: During a full load in Informatica MDM, which table is truncated before new data is inserted to ensure a clean state?
- Base object (_BO) table
- Staging (_STG) table (Correct answer)
- XREF table
- Match result table
Correct answer: Staging (_STG) table
In a full load, the staging _STG table is cleared before the source data is re-staged, ensuring no stale records from prior runs interfere with the incoming data.
Question 3: What is the purpose of the HUB_STATE_IND column set on records in the Informatica MDM staging table?
- Indicates whether the record has been matched and merged
- Tracks the processing state of a staged record (pending, active, deleted) (Correct answer)
- Stores the trust-weighted confidence for the entire record
- Flags records that require manual data steward review
Correct answer: Tracks the processing state of a staged record (pending, active, deleted)
HUB_STATE_IND marks the lifecycle state of a staged record, such as whether it is pending processing, has been loaded, or represents a logical delete from the source.
Question 4: In Informatica MDM, what does a HUB_STATE_IND value of '1' typically represent for a staging record?
- The record is new and pending load into the base object (Correct answer)
- The record is active and has been successfully loaded
- The record represents a delete from the source system
- The record failed validation and is in error state
Correct answer: The record is new and pending load into the base object
A HUB_STATE_IND of 1 indicates the record is new (pending) and has not yet been promoted to the base object by the load job.
Question 5: Which Informatica MDM feature allows a source system to signal that a previously loaded record should be logically removed from the hub during the next load?
- Hard delete flag in the base object
- Delete indicator on the staging record (Correct answer)
- Trust decay configuration
- Match exclusion rule
Correct answer: Delete indicator on the staging record
A delete indicator (or HUB_STATE_IND set to indicate deletion) on a staging record tells the load job to logically remove or deactivate the corresponding base object record.
Question 6: When multiple source systems provide data for the same entity type in Informatica MDM, how does the load job determine which source's value survives for a given attribute?
- The most recently loaded record always wins regardless of source
- Trust scores and validation rules determine the winning value per attribute (Correct answer)
- The source system with the most records automatically dominates
- All source values are concatenated together in the base object
Correct answer: Trust scores and validation rules determine the winning value per attribute
Survivorship during load uses per-attribute trust scores and any configured validation rules to select the best value from competing source systems.
Question 7: What is the effect of setting 'Reject Null Values' on a base object column in Informatica MDM during the load process?
- Records with nulls in that column are automatically assigned a default value
- Records with nulls in that column are rejected and written to the error table (Correct answer)
- Null values are replaced by the value from the previous successful load
- The load job skips null fields and only updates populated attributes
Correct answer: Records with nulls in that column are rejected and written to the error table
When 'Reject Null Values' is enabled for a column, any incoming record containing null in that field is rejected at load time and placed in the error/reject table.
When configuring a source system in Informatica MDM Hub Console, which setting determines the default trust level assigned to records from that source during load?