Data Modeling & Master Data Architecture Flashcards

Which MDM deployment style is characterized by each source system maintaining its own copy of master data while the MDM hub propagates updates?

Answer: Coexistence style

In the coexistence style, source systems retain their own master data copies but synchronize with the MDM hub, allowing gradual adoption.

In Informatica MDM, what is a 'match rule set' and how does it differ from an individual 'match column'?

Answer: A match rule set groups multiple match columns into a logical combination that must collectively satisfy a match, while a match column is a single attribute comparison

A match rule set combines multiple match columns with AND/OR logic to define a compound matching strategy, while individual match columns specify single-field comparison methods.

Which type of MDM architecture would be most appropriate for an organization that wants to enrich master data without altering source system records?

Answer: Analytical MDM

Analytical MDM focuses on creating enriched, consolidated master data for reporting and analytics without modifying source system records.

What is the function of 'tokenization' in Informatica MDM's matching framework?

Answer: Generating standardized match keys from attribute values to improve matching performance and accuracy

Tokenization in MDM generates match tokens (standardized keys) from attributes like name and address, allowing efficient indexing and comparison during the match process.

In Informatica MDM Hub, what is the difference between a 'hard merge' and a 'soft merge'?

Answer: Hard merge permanently merges records with no undo; soft merge marks records as merged but preserves unmerge capability

A hard merge permanently consolidates records in the hub, while a soft (manual) merge can be undone via unmerge operations in Data Director.

Which modeling concept ensures that a single customer entity in MDM can be associated with multiple addresses (home, work, billing) without data redundancy?

Answer: One-to-many child object (e.g., Address child object linked to Customer base object)

A child object linked via a one-to-many relationship allows a single customer master record to have multiple associated address records without repeating customer data.

What is the purpose of 'period-based hierarchy versioning' in Informatica MDM hierarchy management?

Answer: To record how organizational or product hierarchies change over time with effective date ranges

Period-based versioning captures historical hierarchy structures by associating start and end dates with each relationship node, enabling time-travel queries.