MDM Data Governance & Stewardship Frameworks 5 — Questions and Answers
Question 1: Which framework is most commonly referenced when establishing enterprise data governance programs that complement MDM implementations?
- ITIL v4
- DAMA-DMBOK (Data Management Body of Knowledge) (Correct answer)
- TOGAF Architecture Framework
- ISO 27001 Information Security
Correct answer: DAMA-DMBOK (Data Management Body of Knowledge)
DAMA-DMBOK is the primary reference framework for enterprise data management and governance programs, widely used alongside MDM implementations.
Question 2: In Informatica MDM, what is the significance of the 'consolidation indicator' (CONSOLIDATION_IND) on a base object record?
- It shows the percentage of data quality rules the record has passed
- It indicates the consolidation state of a record, such as whether it is a candidate for merge, has been merged, or is the surviving golden record (Correct answer)
- It tracks how many source systems contributed to the record
- It records the last time the record was updated by a steward
Correct answer: It indicates the consolidation state of a record, such as whether it is a candidate for merge, has been merged, or is the surviving golden record
The CONSOLIDATION_IND column indicates a record's state in the consolidation lifecycle—for example, whether it is a merge candidate (4), merged (2), or the master cell (1).
Question 3: What governance challenge does 'party data' management address in MDM, particularly for financial services organizations?
- Managing product catalog hierarchies across subsidiaries
- Maintaining a single, consistent view of customers, counterparties, and legal entities to support KYC, AML, and regulatory compliance (Correct answer)
- Synchronizing transaction records between banking systems
- Managing employee payroll data across multiple HR systems
Correct answer: Maintaining a single, consistent view of customers, counterparties, and legal entities to support KYC, AML, and regulatory compliance
Party data management in financial services MDM focuses on creating a single trusted view of all parties for KYC, AML, and regulatory reporting compliance.
Question 4: When a data governance framework mandates 'data quality SLAs,' what does this mean in an MDM context?
- Service-level agreements defining minimum uptime for the MDM Hub server
- Agreed-upon measurable targets for data quality dimensions (completeness, accuracy, timeliness) that master data must meet (Correct answer)
- Licensing agreements between Informatica and the organization
- Network performance benchmarks for MDM Hub API response times
Correct answer: Agreed-upon measurable targets for data quality dimensions (completeness, accuracy, timeliness) that master data must meet
Data quality SLAs define the minimum acceptable quality thresholds—such as 98% completeness—that master data must meet, making governance commitments measurable.
Question 5: Which Informatica MDM capability allows governance teams to define and enforce business rules that flag master records failing quality thresholds for steward review?
- Stage Jobs
- Informatica Data Quality (IDQ) integration with validation rules (Correct answer)
- Hierarchy Manager relationship rules
- Audit Manager reports
Correct answer: Informatica Data Quality (IDQ) integration with validation rules
Integration with Informatica Data Quality allows governance teams to define validation rules that flag non-compliant master records, routing them to stewards for remediation.
Question 6: In MDM governance, what is the purpose of a 'data stewardship escalation path'?
- To automatically promote junior stewards to senior roles after a set period
- To define the sequence of escalation when a data issue cannot be resolved at a lower stewardship level, ensuring accountability up to executive sponsors (Correct answer)
- To increase the priority of batch MDM jobs during peak hours
- To route duplicate match alerts to external data quality vendors
Correct answer: To define the sequence of escalation when a data issue cannot be resolved at a lower stewardship level, ensuring accountability up to executive sponsors
An escalation path defines how unresolved data issues move up through stewardship levels to governance councils or executive sponsors when lower-level resolution fails.
Question 7: What is the recommended approach for governing 'relationship data' (e.g., customer-to-account links) in Informatica MDM's Hierarchy Manager?
- Store relationship data only in source systems and never in the MDM Hub
- Define relationship types with start/end dates, relationship attributes, and governance rules to manage hierarchical and network relationships as first-class governed data (Correct answer)
- Use flat file exports to represent all relationship data outside of the MDM Hub
- Relationships are automatically derived from base object foreign keys without governance configuration
Correct answer: Define relationship types with start/end dates, relationship attributes, and governance rules to manage hierarchical and network relationships as first-class governed data
Hierarchy Manager treats relationships as governed entities with their own attributes, validity periods, and governance rules, making relationship data a first-class citizen in MDM governance.
Which framework is most commonly referenced when establishing enterprise data governance programs that complement MDM implementations?