MDM - Informatica Master Data Management MDM Architecture and Datamodel Questions and Answers — Questions and Answers
Question 1: In the Informatica MDM architecture, which component is primarily responsible for executing data cleansing, matching, and batch jobs like load and revalidation?
- Hub Console
- Hub Store
- Process Server (Correct answer)
- Hub Server
Correct answer: Process Server
The Process Server is the component that handles intensive data processing tasks. It interfaces with cleanse engines, executes match processes to identify duplicates, and runs various batch jobs required for data management within the MDM Hub.
Question 2: A data steward needs to model a 'Customer' entity that will serve as the single source of truth, consolidating data from multiple source systems. Which type of table in the Informatica MDM data model should be used for this purpose?
- Landing Table
- Base Object (Correct answer)
- Staging Table
- Cross-reference Table
Correct answer: Base Object
The Base Object is the core table in the MDM data model where the consolidated, master version of the data (the 'golden record') is stored. It represents the single source of truth for a business entity after data has been cleansed, matched, and merged.
Question 3: A company wants to implement a rule stating that a customer's 'Date of Birth' from the CRM system is more reliable than the same information from the Billing system. Which MDM Hub feature is used to configure this survivorship logic?
- Validation Rules
- Hierarchy Manager
- State Management
- Trust Scores (Correct answer)
Correct answer: Trust Scores
Trust Scores are assigned to source systems for specific attributes to determine reliability. A higher trust score indicates greater preference. In the survivorship process, the MDM Hub uses these scores to decide which source system's value will populate the 'golden record' in the Base Object.
Question 4: During the data loading process in Informatica MDM, what is the primary function of a Staging Table?
- To store the final, consolidated 'golden records' of master data.
- To act as the initial entry point for raw, untransformed data from source systems.
- To hold cleansed, standardized, and validated data before it is loaded into the Base Object. (Correct answer)
- To store historical versions and the lineage of master data records.
Correct answer: To hold cleansed, standardized, and validated data before it is loaded into the Base Object.
Staging Tables serve as an intermediate area where data from Landing Tables is processed. This is where data cleansing, standardization, and data quality checks occur to prepare the data for loading into the final Base Object.
Question 5: Which of the following best describes the relationship between a Base Object, Staging Tables, and source systems in a typical Informatica MDM implementation?
- One Base Object can have only one Staging Table, which receives data from a single source system.
- Multiple Base Objects are mapped to a single Staging Table for data consolidation.
- A Base Object consolidates data, and there is typically one Staging Table for each source system that contributes data to that Base Object. (Correct answer)
- Staging Tables are created from Base Objects to push master data back to source systems.
Correct answer: A Base Object consolidates data, and there is typically one Staging Table for each source system that contributes data to that Base Object.
The standard data model architecture involves a central Base Object for the master record. To populate this Base Object, data is first brought into source-specific Staging Tables. Therefore, a single Base Object will have multiple associated Staging Tables, one for each contributing source system.
Question 6: An organization needs to model complex, multi-level relationships between its 'Organization' and 'Contact' master records, such as corporate ownership structures and reporting lines. Which Informatica MDM feature is specifically designed to manage these types of connections?
- Trust Framework
- State Management
- Hierarchy Manager
- Message Queues (Correct answer)
Correct answer: Message Queues
The Hierarchy Manager (HM) is the tool within Informatica MDM used to define, manage, and visualize complex relationships and hierarchical structures between master data entities. It allows for the creation of parent-child and other complex associations, like organizational charts or product catalogs.
MDM - Informatica Master Data Management MDM Architecture and Datamodel Questions and Answers
In the Informatica MDM architecture, which component is primarily responsible for executing data cleansing, matching, and batch jobs like load and revalidation?