CDMP-RMD practice question 16 of 35

A key capability to quickly onboard new data suppliers and subscribers to a MDM solution is which of the following?

Full set: 100 questions
Answer options
A: Data format and transfer flexibility Correct answer
B: Source system conformance to a single standard data input format
C: Requiring only delta loads of changed data attributes
D: Encrypting all personal information
E: Subscriber conformance to a single standard data output format
Correct Answer:
A. Data format and transfer flexibility
Explanation

To quickly onboard new data suppliers and subscribers, an MDM solution must be adaptable. Data format and transfer flexibility is the key capability that enables this. It allows the MDM system to ingest data from various sources in their native formats (e.g., XML, JSON, CSV) and via different protocols (e.g., API, FTP, message queue). Similarly, it can provide master data to subscribers in the formats and methods they require. This adaptability minimizes the need for source and target systems to undergo custom development to conform to a rigid, single standard, thereby significantly accelerating the integration and onboarding process.

Why Incorrect

B. Source system conformance to a single standard data input format: This approach is rigid and forces suppliers to change their systems, which significantly slows down, not accelerates, onboarding.
C. Requiring only delta loads of changed data attributes: This is an operational efficiency feature for ongoing synchronization, not the primary capability that enables the initial rapid onboarding of a new system.
D. Encrypting all personal information: This is a critical security and compliance requirement, but it does not directly contribute to the speed of integrating new data partners.
E. Subscriber conformance to a single standard data output format: Similar to option B, this forces data consumers to adapt, creating an integration bottleneck and slowing down the adoption of the MDM service. ---

References

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

Reference: Chapter 11, Section 3.4.2, "MDM Integration Architecture," pp. 366-367.

Quote/Concept: This section describes the necessity of components like an Enterprise Service Bus (ESB), APIs, and data integration (ETL) tools to connect the MDM hub with a variety of source and consuming systems. The inherent purpose of these architectural components is to handle the heterogeneity of formats and protocols in the enterprise landscape, which directly supports the principle of flexibility for faster integration.

2. Loshin, D. (2009). Master Data Management. Morgan Kaufmann (Elsevier).

Reference: Chapter 10, "Coupling and Cohesion," Section on "Adapters and Connectors," pp. 191-192.

Quote/Concept: Loshin explains that to reduce the complexity and time of integration, MDM solutions should employ adapters and connectors. These components act as translators, allowing the MDM hub to communicate with source and target applications without requiring those applications to be rewritten. This "loose coupling" achieved through flexible adapters is fundamental to rapid onboarding.

3. Spruit, M., & Pietzka, K. (2015). MDM: The key to unlock the value of big data. International Journal of Information Management, 35(2), 268-278.

Reference: Section 3.2, "MDM Architecture," p. 272.

DOI: https://doi.org/10.1016/j.ijinfomgt.2014.12.002

Quote/Concept: The paper discusses service-oriented architecture (SOA) principles in the context of MDM. A key benefit of a service-oriented approach is that it "enables a loose coupling of systems," which allows for greater flexibility in how different systems (suppliers and subscribers) interact with the MDM hub. This architectural flexibility is essential for accommodating new systems quickly.

Scroll to Top