MDM Data Governance & Quality Management 5 — Questions and Answers
Question 1: Which Informatica MDM capability allows governance teams to define rules that automatically flag records for review when an address field changes more than a configured number of times within a set period?
- Data Stewardship workflows with conditional triggers based on change history (Correct answer)
- Match rule frequency thresholds in the consolidation engine
- Batch Viewer anomaly detection reports
- Schema Manager column-level change locks
Correct answer: Data Stewardship workflows with conditional triggers based on change history
Conditional workflow triggers can be set to monitor field change frequency and automatically escalate suspicious update patterns to stewardship queues.
Question 2: In Informatica MDM Hub, which table type holds the integrated, de-duplicated master records that represent the best version of truth?
- Base object table (Correct answer)
- Landing table
- Staging table
- Cross-reference (XREF) table
Correct answer: Base object table
The base object table stores the golden records—the consolidated, survivorship-resolved master data that represents the authoritative version of each entity.
Question 3: A data quality scorecard in Informatica MDM governance shows a 'conformity' score. What does this measure?
- The degree to which data values adhere to defined format standards and business rules (Correct answer)
- The percentage of records that successfully matched to an existing golden record
- The number of source systems contributing data to the master store
- The average trust score across all source systems for a given entity
Correct answer: The degree to which data values adhere to defined format standards and business rules
Conformity measures whether data values follow prescribed patterns, formats, and business rules, such as phone numbers matching a required format.
Question 4: When a data governance policy mandates 'data minimization' for GDPR compliance in Informatica MDM, what is the primary implementation approach?
- Restricting which attributes are collected and stored in base objects, removing non-essential personal fields (Correct answer)
- Reducing the number of source systems allowed to feed into MDM Hub
- Limiting the batch size of records processed per load cycle
- Setting all personal attribute trust scores to zero
Correct answer: Restricting which attributes are collected and stored in base objects, removing non-essential personal fields
Data minimization for GDPR requires collecting only necessary personal data, implemented in MDM by removing non-essential personal attribute columns from the base object schema.
Question 5: Which Informatica MDM feature enables a governance team to define hierarchical relationships between master data records for organizational reporting?
- Hierarchy Manager (Correct answer)
- Relationship Base Object
- Package Manager
- Consolidation Indicator
Correct answer: Hierarchy Manager
Hierarchy Manager in Informatica MDM allows governance teams to define, manage, and visualize parent-child and many-to-many relationships between master data entities.
Question 6: In Informatica MDM, what is the governance significance of the 'Hub State Indicator' (HUB_STATE_IND) column on a base object record?
- It indicates whether the record is active, merged into another record, or marked as deleted, controlling its visibility in queries (Correct answer)
- It stores the trust score of the source system that contributed the record
- It identifies which batch job last updated the record
- It flags whether the record has passed all data quality checks
Correct answer: It indicates whether the record is active, merged into another record, or marked as deleted, controlling its visibility in queries
HUB_STATE_IND governs the lifecycle state of a base object record—active (1), merged-away (0), or deleted—determining whether it participates in MDM operations.
Question 7: A governance requirement states that all changes to financial master data in Informatica MDM must be reversible within 30 days. Which built-in capability best supports this requirement?
- Cross-reference (XREF) tables and history tables that preserve source contributions and prior golden record states (Correct answer)
- Nightly batch job logs stored in the Batch Viewer for 30 days
- Schema Manager's column-version snapshots
- Match rule rollback scripts maintained by the MDM administrator
Correct answer: Cross-reference (XREF) tables and history tables that preserve source contributions and prior golden record states
XREF tables retain all source system contributions, and _HIST tables track historical golden record states, enabling reconstruction of past data states for rollback or audit.
MDM Data Governance & Quality Management 5
Which Informatica MDM capability allows governance teams to define rules that automatically flag records for review when an address field changes more than a configured number of times within a set period?