Practice Test Geeks(MDM) Informatica Master Data Management Certification Practice Test
← All MDM Flashcard Decks

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

  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?

    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.

  2. During a full load in Informatica MDM, which table is truncated before new data is inserted to ensure a clean state?

    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.

  3. What is the purpose of the HUB_STATE_IND column set on records in the Informatica MDM staging table?

    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.

  4. In Informatica MDM, what does a HUB_STATE_IND value of '1' typically represent for a staging record?

    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.

  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?

    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.

  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?

    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.

  7. What is the effect of setting 'Reject Null Values' on a base object column in Informatica MDM during the load process?

    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.