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

Data Modeling & Master Data Architecture 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 Data Modeling & Master Data Architecture flashcards as text

  1. In Informatica MDM, which process determines the final attribute values of the golden record by selecting among competing source system values?

    Answer: Survivorship

    Survivorship rules evaluate competing attribute values from multiple source systems and select the best value based on trust scores, recency, or custom logic.

  2. Which Informatica MDM feature allows a data model to support multiple entity types (e.g., Person and Organization) under a single base object using a type discriminator?

    Answer: Subtype modeling using a base object with a record type column

    Subtype modeling uses a single base object with a discriminator column (e.g., PARTY_TYPE) to distinguish between entity types, reducing model complexity.

  3. What is the risk of setting match thresholds too low in an Informatica MDM match configuration?

    Answer: Increased false positives — non-duplicate records are incorrectly merged

    Setting match thresholds too low increases false positives, causing distinct records to be incorrectly identified as duplicates and merged.

  4. In Informatica MDM, what does the 'source system' configuration in Hub Console primarily define?

    Answer: The trusted source of each attribute and the contribution rules for that system's data in the hub

    Source system configuration defines the system's trust level, contribution rules, and how its data interacts with other systems' records during consolidation.

  5. Which normalization strategy is typically AVOIDED in MDM base object design because it hinders match performance?

    Answer: Storing names as a single full-name field instead of first/last components

    Storing a full name as a single concatenated field prevents effective tokenization and fuzzy matching on individual name components.

  6. In the context of Informatica MDM multi-domain architecture, what challenge does a 'shared business entity' (e.g., a shared Address object) across Customer and Supplier domains introduce?

    Answer: It creates governance complexity because changes to the shared entity affect multiple domains and stewardship teams

    A shared entity introduces cross-domain governance challenges because modifications to its structure or rules impact all domains and their respective data stewards.

  7. What is the purpose of the 'delta detection' step in Informatica MDM's load process?

    Answer: To identify new or changed source records since the last load, avoiding reprocessing of unchanged data

    Delta detection compares incoming source records against the previous load to identify only new or changed records, improving load efficiency.