What type of interactive system model is most often used for Master Data Management?
Answer : A
The hub-and-spoke model is most often used for Master Data Management because it provides a central hub where master data is maintained, while the spokes represent different systems or applications that interact with the hub. This model allows for efficient management, synchronization, and distribution of master data across the enterprise, ensuring consistency and quality.
DMBOK (Data Management Body of Knowledge), 2nd Edition, Chapter 11: Reference & Master Data Management.
The Data Warehouse Toolkit: The Definitive Guide to Dimensional Modeling by Ralph Kimball and Margy Ross.
Why is a historical perspective of Master Data important?
Answer : E
Historical Perspective of Master Data: Maintaining historical data about master data objects is crucial for various reasons.
Reasons for Importance:
Provides an audit trail: Keeping historical data allows organizations to track changes and understand the evolution of data over time, which is essential for auditing purposes.
May be required in litigation cases: Historical data can serve as evidence in legal disputes, demonstrating the state of data at specific points in time.
Attributes about Master Data subjects evolve over time: As entities change, such as customers moving or changing names, maintaining historical data allows for accurate tracking of these changes.
Enables business analytics to determine the root cause of behavioral changes: Historical data can help in analyzing trends and identifying reasons for changes in business metrics or customer behavior.
Conclusion: All the provided reasons collectively highlight the importance of maintaining a historical perspective of master data.
DMBOK Guide, sections on Master Data Management and Data Governance.
CDMP Examination Study Materials.
Does an organization have to agree to a single definition for Master Data?
Answer : B
For effective Master Data Management, an organization must agree on a single, standard definition of master data. Here's why:
Consistency:
Single Definition: A standardized definition ensures consistency across different departments and systems.
Avoids Confusion: Prevents discrepancies and misunderstandings regarding what constitutes master data.
Data Quality and Governance:
Unified Approach: A single definition supports unified data governance policies and data quality standards.
Data Integration: Facilitates easier data integration and interoperability across various systems and processes.
Business Efficiency:
Aligned Objectives: Ensures all parts of the organization are aligned in their understanding and use of master data, leading to more efficient operations and decision-making.
Data Management Body of Knowledge (DMBOK), Chapter 7: Master Data Management
DAMA International, 'The DAMA Guide to the Data Management Body of Knowledge (DMBOK)'
When 2 records are not matched when they should have been matched, this condition is referred to as:
Answer : C
Definitions and Context:
False Positive: This occurs when a match is incorrectly identified, meaning records are deemed to match when they should not.
True Positive: This is a correct identification of a match, meaning records that should match are correctly identified as matching.
False Negative: This occurs when a match is not identified when it should have been, meaning records that should match are not matched.
True Negative: This is a correct identification of no match, meaning records that should not match are correctly identified as not matching.
Anomaly: This is a generic term that could refer to any deviation from the norm and does not specifically address the context of matching records.
The question asks about a scenario where two records should have matched but did not. This is the classic definition of a False Negative.
In data matching processes, this is a critical error because it means that the system failed to recognize a true match, which can lead to fragmented and inconsistent data.
DAMA-DMBOK: Data Management Body of Knowledge, 2nd Edition, Chapter 11: Master and Reference Data Management.
ISO 8000-2:2012, Data Quality - Part 2: Vocabulary.
What characteristics does Reference data have that distinguish it from Master Data?
Answer : C
Reference data and master data are distinct in several key characteristics. Here's a detailed explanation:
Reference Data Characteristics:
Stability: Reference data is generally less volatile and changes less frequently compared to master data.
Complexity: It is less complex, often consisting of simple lists or codes (e.g., country codes, currency codes).
Size: Reference data sets are typically smaller in size than master data sets.
Master Data Characteristics:
Volatility: Master data can be more volatile, with frequent updates (e.g., customer addresses, product details).
Complexity: More complex structures and relationships, involving multiple attributes and entities.
Size: Larger in size due to the detailed information and numerous entities it encompasses.
Data Management Body of Knowledge (DMBOK), Chapter 7: Master Data Management
DAMA International, 'The DAMA Guide to the Data Management Body of Knowledge (DMBOK)'
For MDMs. what is meant by a classification scheme?
Answer : A
In Master Data Management (MDM), a classification scheme refers to a structured way of organizing data by using codes that represent a controlled set of values. These codes help in categorizing and standardizing data, making it easier to manage, search, and analyze.
DAMA-DMBOK: Data Management Body of Knowledge (2nd Edition), Chapter 11: Reference and Master Data Management.
'Master Data Management and Data Governance' by Alex Berson and Larry Dubov.
Within the Corporate Information Factory, what data is used to understand transactions?
Answer : C
In the context of the Corporate Information Factory, understanding transactions involves integrating various types of data to get a comprehensive view. Master Data (core business entities), Reference Data (standardized information), and External Data (information sourced from outside the organization) are essential for providing context and enriching transactional data.
DAMA-DMBOK: Data Management Body of Knowledge (2nd Edition), Chapter 3: Data Architecture and Chapter 11: Reference and Master Data Management.
'Building the Data Warehouse' by W.H. Inmon, which introduces the Corporate Information Factory concept.