CDMP-RMD practice question 2 of 35

Which of the following is NOT part of MDM Lifecycle Management?

Full set: 100 questions
Answer options
A: Establishing recovery and backup rules Correct answer
B: Reconciling and consolidating data
C: Identifying multiple instances of the same entity
D: Identifying improperly matched or merged instances of data
E: Maintaining cross-references to enable information integration
Correct Answer:
A. Establishing recovery and backup rules
Explanation

MDM Lifecycle Management encompasses the processes directly involved in managing a master data entity from creation to retirement. These core activities include identifying duplicate instances across systems, reconciling conflicting values, consolidating them into a single "golden record," and maintaining cross-references to source systems. Establishing recovery and backup rules, while critical for the underlying technology that supports MDM, is not a step in the lifecycle of the data entity itself. This function is part of the broader Data Storage and Operations knowledge area, which ensures the resilience and availability of the MDM system, rather than a process for managing the master data content.

Why Incorrect

B. Reconciling and consolidating data is the central MDM process of creating an authoritative, single version of the truth from disparate sources.
C. Identifying multiple instances of the same entity (i.e., matching) is the foundational step in any MDM initiative to detect and manage data duplication.
D. Identifying improperly matched or merged instances is a crucial data stewardship and quality control activity within the ongoing management and maintenance of master data.
E. Maintaining cross-references is a key function that links the master record to its source systems, enabling data lineage, integration, and synchronization.

References

1. DAMA International. (2017). DAMA-DMBOK: Data Management Body of Knowledge (2nd ed.). Technics Publications.

Chapter 12, Section 3.3, "Master Data Record Lifecycle," describes the processes for managing the master data entity, which implicitly include matching (C), consolidation (B), stewardship (D), and integration via cross-references (E).

Chapter 7, "Data Storage and Operations," Section 4.2, "Database Backup and Recovery," explicitly covers the establishment of backup and recovery procedures as a distinct operational activity, separate from the lifecycle management of specific data types like master data. This separation confirms that backup/recovery is not considered part of the MDM lifecycle itself.

Scroll to Top