Questions RMD10-035–051
RMD10-035 — MDM Processing · Standard · Distinguish
Which best describes enrichment in the MDM process? - A. Translating source IDs to Global IDs only. - B. Deleting all nonmatching records. - C. Supplementing records with additional trusted data to improve the master view. - D. Building a Reference Data taxonomy.
RMD10-036 — Entity Resolution · Foundational · Recall
What is entity resolution? - A. Selecting the correct code from a Reference Data list. - B. Choosing a data-sharing architecture. - C. Setting an SLA for data availability. - D. Determining whether two references to real-world objects represent the same entity or different entities.
RMD10-037 — Entity Resolution · Standard · Distinguish
Two different customers are incorrectly linked to one enterprise identifier. What happened? - A. False positive match - B. False negative match - C. Reference Data collision - D. Successful match-link
RMD10-038 — Entity Resolution · Standard · Distinguish
The same real-world customer remains under two enterprise identifiers after matching. What happened? - A. False positive match - B. False negative match - C. Golden Record creation - D. Reference Data crosswalk
RMD10-039 — Entity Resolution · Standard · Distinguish
A matcher uses fixed parsing, standardization patterns and explicit scoring rules that always yield the same result for the same inputs. What approach is this? - A. Probabilistic matching - B. Match-link - C. Deterministic matching - D. Affiliation management
RMD10-040 — Entity Resolution · Difficult · Distinguish
A matcher is trained on sample outcomes and adjusts statistical probabilities of record equivalence as more data is analyzed. What approach is this? - A. Deterministic matching - B. Duplicate identification workflow - C. Reference Data standardization - D. Probabilistic matching
RMD10-041 — Entity Resolution · Standard · Distinguish
Which activity finds records that may refer to the same entity before the final identity decision? - A. Candidate identification / matching - B. Affiliation management - C. Data sharing - D. Reference Data governance
RMD10-042 — Entity Resolution · Difficult · Apply
Why should an MDM program preserve match history? - A. To ensure every match is permanent once made. - B. Incorrect match decisions must be reversible, and history supports unmerge/remerge, metrics and rule improvement. - C. To eliminate the need for stewardship. - D. To convert Master Data into Reference Data.
RMD10-043 — Entity Resolution · Standard · Apply
The organization wants likely duplicates flagged for Data Steward review with no automatic merge. Which workflow fits? - A. Match-merge - B. Match-link - C. Duplicate identification - D. Transaction Hub
RMD10-044 — Entity Resolution · Standard · Apply
Records should be associated with a master identity but source attributes must remain unchanged and reversal should be easy. Which workflow fits? - A. Match-merge - B. Duplicate identification - C. Consolidated architecture - D. Match-link
RMD10-045 — Entity Resolution · Difficult · Apply
Three source records clearly represent one entity and the business needs a unified reconciled profile. Which workflow fits? - A. Match-merge - B. Match-link - C. Duplicate identification - D. Reference crosswalk
RMD10-046 — Entity Resolution · Difficult · Understand
What makes match-merge especially complex? - A. It never uses business rules. - B. The organization must decide which source values can be trusted to survive into the unified record, and reversal of a false merge can be costly. - C. It cannot combine data from multiple sources. - D. It eliminates the need for Global IDs.
RMD10-047 — Identifier Management · Standard · Distinguish
What is a Global ID in Chapter 10? - A. The original key from a source system. - B. A Reference Data code such as US or GB. - C. An MDM-assigned and maintained unique identifier for a reconciled entity instance. - D. A data-quality score.
RMD10-048 — Identifier Management · Standard · Distinguish
What does x-ref management maintain? - A. Only the surviving attribute values in a Golden Record. - B. The list of allowed Reference Data values. - C. The SLA between data providers and consumers. - D. The relationship and history between source-system IDs and the Global ID.
RMD10-049 — Identifier Management · Difficult · Understand
Why should only one authorized solution generate Global IDs? - A. To preserve uniqueness and avoid duplicate enterprise identifiers across the MDM environment. - B. Because source systems may never have their own IDs. - C. Because Global IDs are Reference Data. - D. Because a registry cannot use Global IDs.
RMD10-050 — Relationships · Standard · Distinguish
When is affiliation management preferable to a simple parent-child relationship? - A. When no relationship exists between entities. - B. When flexible typed real-world associations are needed and hierarchy may need to be derived for different uses. - C. When managing a flat Reference Data list. - D. When assigning the first Global ID.
RMD10-051 — Architecture · Standard · Apply
A global company wants an enterprise index of Master Data but wants minimal change to the systems of record. Which architecture is the strongest candidate? - A. Transaction Hub - B. Consolidated - C. Registry - D. Reference Data taxonomy