Questions RMD10-052–068
RMD10-052 — Architecture · Standard · Apply
Applications should access and update Master Data only through a central hub that becomes the authoritative Master Data system. Which approach fits? - A. Registry - B. Consolidated - C. System of Reference only - D. Transaction Hub
RMD10-053 — Architecture · Standard · Apply
Source applications continue to maintain their own Master Data, but consumers need one stored enterprise view without directly querying every source. Which approach fits? - A. Consolidated - B. Registry - C. Transaction Hub - D. Simple Reference list
RMD10-054 — Architecture · Difficult · Understand
What is a key trade-off of the Consolidated approach? - A. It forces all writes through the hub. - B. It limits impact on systems of record but introduces replication and latency between sources and the shared hub. - C. It requires no central repository. - D. It eliminates the need for semantic reconciliation.
RMD10-055 — MDM Activities · Standard · Recall
Which activity comes after evaluating/assessing MDM data sources? - A. Establish governance policies first and skip architecture. - B. Publish Master Data before modeling. - C. Define the architectural approach - D. Delete source identifiers.
RMD10-056 — RDM Activities · Difficult · Apply
What should an RDM architectural approach explicitly consider? - A. Only the number of rows in the code table. - B. Only probabilistic entity matching thresholds. - C. Only whether a data warehouse exists. - D. Volatility, update frequency, consumption models, historical versions, vendor delivery/integration, manual stewardship updates and approval/notification workflow.
RMD10-057 — RDM Activities · Standard · Understand
Which Metadata is useful for Reference Data stewardship? - A. Steward, originating organization, update frequency/schedule, consuming processes and whether history must be retained. - B. Only the current row count. - C. Only Global ID mappings. - D. Only transaction volume.
RMD10-058 — Implementation · Standard · Understand
Why should MDM/RDM be implemented incrementally through a roadmap? - A. Because shared data programs cannot have enterprise architecture. - B. The capabilities require specialized business/technical knowledge and should be prioritized by business need under an overall architecture. - C. Because only one Reference Data set may be governed at a time. - D. Because governance is unnecessary until the last project.
RMD10-059 — Implementation · Difficult · Apply
Which factor set best fits Chapter 10 architecture selection? - A. Only database brand and license cost. - B. Only the number of Data Stewards. - C. Organizational structure, number of SORs, governance implementation, access/latency importance, and number of consumers/applications. - D. Only the number of Reference Data rows.
RMD10-060 — Implementation · Standard · Apply
Why monitor Reference/Master Data movement? - A. To avoid documenting data lineage. - B. To eliminate all Data Quality rules. - C. To make every source a Transaction Hub. - D. To show sharing/usage and lineage, support root-cause analysis, measure ingestion effectiveness/latency and validate integration rules/transformations.
RMD10-061 — Implementation · Standard · Recall
Which sequence best represents the Chapter 10 Reference Data change process? - A. Receive request → identify stakeholders → identify impact → decide/approve → update → communicate/inform - B. Update → notify → assess impact - C. Delete old values → create new values → skip communication - D. Match → merge → assign Global ID
RMD10-062 — Implementation · Standard · Understand
What is the purpose of a data-sharing agreement in Chapter 10? - A. To replace Data Governance approval. - B. To specify what Reference/Master Data can be shared, under what conditions, and support accountability when quality or availability issues arise. - C. To define only database column mappings. - D. To guarantee every upstream value is error-free.
RMD10-063 — Organization · Difficult · Apply
Why can organizational change be difficult in MDM/RDM? - A. Because Reference and Master Data should remain department-specific. - B. Because Data Stewards should make every decision alone. - C. Teams may resist relinquishing local control of data/processes even when enterprise sharing reduces inconsistency and risk. - D. Because technology cannot share data across systems.
RMD10-064 — Governance · Difficult · Apply
Which decision belongs squarely in Chapter 10 governance? - A. Which employee should personally write each SQL statement. - B. Whether matching history should be deleted after each run. - C. Whether shared data should avoid all privacy/security requirements. - D. Which sources to integrate, which Data Quality and conditions-of-use rules to enforce, what to monitor, and what approval gates apply.
RMD10-065 — Metrics · Standard · Distinguish
Which metric family tracks the rate and lineage of changes and can help tune MDM algorithms? - A. Data change activity - B. Data Steward coverage - C. Total Cost of Ownership - D. Sharing volume and usage
RMD10-066 — Metrics · Standard · Distinguish
Which metric identifies what systems contribute data and what business areas subscribe to the shared environment? - A. Data Quality and compliance - B. Data ingestion and consumption - C. Data Steward coverage - D. Total Cost of Ownership
RMD10-067 — Metrics · Standard · Distinguish
Which metric best reveals whether a subject area lacks an accountable steward or responsible group? - A. SLA adherence - B. Data change activity - C. Data Steward coverage - D. Sharing volume
RMD10-068 — Metrics · Expert-discrimination · Apply
A Master Data program reports only “10 million records in the hub.” Which measurement set would better demonstrate Chapter 10 effectiveness? - A. Only the total record count - B. Only the number of matching rules - C. Only the number of source systems - D. Data Quality/compliance, change activity, ingestion/consumption, SLA adherence, steward coverage, TCO, and sharing volume/usage.