CDMP-RMD practice question 30 of 35
The concept of tracking the number of MDM subject areas and source system attributes Is referred to as:
Full set: 100 questionsThe term "Subject Area and Attribute Scope and Coverage" refers to the metrics used to define and track the extent of a Master Data Management (MDM) program. "Scope" defines which master data subject areas (e.g., Customer, Product) and which specific attributes within them are under management. "Coverage" measures how many of the source systems and their relevant attributes have been incorporated into the MDM hub. Tracking these numbers is a fundamental activity in managing the MDM program's roadmap, progress, and maturity.
A. Publish and Subscribe: This is a data integration architectural pattern where message producers (publishers) do not send messages directly to specific receivers (subscribers), but to channels. It is not a concept for tracking scope.
B. Hub and Spoke: This is a common MDM implementation architecture where a central "hub" stores the master data, and "spokes" connect to source and consuming systems. It describes data flow, not scope measurement.
C. Mapping and Integration: These are core processes within an MDM implementation that involve linking source data elements to the master data model and the technical work of data movement. They are activities, not the concept of tracking scope.
1. DAMA International. (2017). DAMA-DMBOK: Data Management Body of Knowledge (2nd ed.). DAMA International.
Chapter 12, Section 3.2, "MDM Program Scope": This section details the importance of defining the scope of an MDM program by identifying the subject areas (domains) to be managed.
Chapter 12, Section 4.2, "Define Master Data": This section discusses the process of identifying critical data elements (attributes) and their authoritative sources, which is fundamental to measuring attribute scope and coverage. The combination of these concepts forms the basis for tracking "Subject Area and Attribute Scope and Coverage."
2. Berson, A., & Dubov, L. (2011). Master Data Management and Data Governance (2nd ed.). McGraw-Hill.
Chapter 4, "MDM Architecture": This chapter discusses defining the scope of MDM initiatives, emphasizing the need to identify and prioritize data domains (subject areas) and the key attributes within them as a foundational step for architecture and implementation. This directly relates to tracking scope and coverage.
Keep practicing
Take the free CDMP-RMD practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other CDMP-RMD practice questions
- Question 1Which is NOT considered a type of Master Data relationship?
- Question 2Which of the following is NOT part of MDM Lifecycle Management?
- Question 3When establishing a MOM. what is the benefit of doing data profiling?
- Question 4Which of the following are reasons why marketing is important to a MDM program?
- Question 5Master Data and metadata ran both he used to aggregate dat a. Master Data require* that t…
- Question 6The 3 primary categories of components in a MDM framework are:
