Compare and Contrast the Various Techniques, Approaches and Considerations for Implementing Master Data Management Solutions (e.g., MDM Implementation Styles, Harmonizing and Consolidating Data from Multiple Sources, Establishing Data Survivorship Rules, Thresholds & Weights, Leveraging External Reference Data for Enrichment, Canonical Modeling Techniques, Hierarchy Management). DATA-ARCHITECT Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   An organization wants to identify duplicate customer records across multiple systems but does not need to store a consolidated master record. They only need a cross-reference of which records refer to the same customer. Which MDM implementation style should they choose?

   • ATransactional style
   • BRegistry style
   • CCo-existence style
   • DConsolidation style
   Reveal Solution Discussion Select an answer first
2. 12expert · hard

   A bank is consolidating customer data from two legacy systems. System A has high-quality, verified data but only covers 60% of customers. System B covers 100% of customers but has frequent data-entry errors. The matching algorithm identifies duplicates with a confidence score, and the bank needs to define survivorship rules. The data architect must balance data quality with coverage. Which survivorship strategy is most appropriate?

   • ACreate a survivorship rule that randomly selects between System A and System B for each field
   • BAlways merge records by taking the most recently updated field from either system
   • CUse System B as the primary source for all attributes because it has complete coverage
   • DUse System A as the primary source for all attributes when available, and fall back to System B only for customers not in System A
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A healthcare organization is consolidating patient records from two clinics. The matching process identifies a pair of records with a confidence score of 85 out of 100, but a data steward notices that the records have different middle names and different addresses. The organization's policy requires a confidence score of at least 90 to auto-merge records. What should the data architect recommend?

   • ALower the threshold to 80 so the records can be auto-merged
   • BRoute the pair to a data steward for manual review and potential merge
   • CAuto-merge the records because the score is above 80
   • DReject the match and keep the records separate permanently
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   In record matching, what does the 'threshold' represent?

   • AThe minimum similarity score required to consider two records a match
   • BThe weight assigned to a particular field
   • CThe number of fields that must be identical for a match
   • DThe maximum number of records that can be matched in a single run
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A data architect is designing an MDM solution for a company that has just acquired another firm. The two companies have different customer data models and different product hierarchies. The architect needs to create a unified view for reporting while allowing each company to continue operating its own systems. Which approach best balances integration and operational independence?

   • ACreate separate MDM hubs for each company and never share data
   • BImplement a canonical model for customers and products, and use a co-existence style to synchronize with both companies' systems
   • CForce both companies to adopt a single new system and retire the legacy systems
   • DBuild a registry that stores only IDs and pointers, with no canonical model
   Reveal Solution Discussion Select an answer first