CDMP-RMD Exam Dumps : Reference And Master Data Management Exam

The Reference Data Change Request Process typically involves the following sub-processes:

Receive Change Request:

Initiation: The process begins with the receipt of a change request, formally logged and acknowledged.

Identify Stakeholder:

Stakeholder Identification: Identifying all relevant stakeholders who need to be involved or informed about the change.

Identify Impact:

Impact Analysis: Assessing the potential impact of the requested change on existing systems, processes, and data.

Decide and Communicate:

Decision Making: Reviewing the change request, making a decision, and communicating the outcome to stakeholders.

Excluded Step - Monitor Database Change: While monitoring database changes is important for overall data management, it is not typically part of the specific change request process for reference data. This step pertains more to ongoing operational monitoring rather than the change request workflow.

References:

Data Management Body of Knowledge (DMBOK), Chapter 6: Data Development & Maintenance

DAMA International, "The DAMA Guide to the Data Management Body of Knowledge (DMBOK)"

In a Consolidated style MDM (Master Data Management) approach, data from multiple source systems is integrated into a single consolidated repository. This consolidated repository acts as the authoritative source for master data, often referred to as the "system of record." The system of record maintains the most accurate, up-to-date, and comprehensive view of master data. Key traits of this approach include:

Centralization: All master data is centralized in one repository, which simplifies data management and governance.

Consistency: Ensures that all users and systems access the same consistent set of master data.

Data Quality: Enhances data quality through data cleansing, deduplication, and validation processes.

Single Source of Truth: Serves as the definitive source for master data, reducing discrepancies and inconsistencies across the organization.

References:

DAMA-DMBOK: Data Management Body of Knowledge, 2nd Edition.

"Master Data Management and Data Governance" by Alex Berson and Larry Dubov.

Planned control activities are not considered master data. Here’s why:

Master Data Examples:

Categories and Lists: Master data typically includes lists and categorizations that are used repeatedly across multiple business processes and systems.

Examples: Product categories, account codes, country codes, and currency codes, which are relatively stable and broadly used.

Planned Control Activities:

Process-Specific: Planned control activities pertain to specific actions and checks within business processes, often linked to operational or transactional data.

Not Repeated Data: They are not reused or referenced as a stable entity across different systems.

References:

Data Management Body of Knowledge (DMBOK), Chapter 7: Master Data Management

DAMA International, "The DAMA Guide to the Data Management Body of Knowledge (DMBOK)"