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 4)

Questions 16–20

1. 16application · medium

   A data architect is configuring a matching engine to identify duplicate customer records across two source systems. The matching algorithm assigns a weight of 40 to exact last name match, 30 to exact first name match, 20 to exact postal code match, and 10 to exact birth date match. The system flags a match as a duplicate when the total score is at least 70. Two records share the same last name, first name, and postal code, but have different birth dates. What is the total match score, and will the records be flagged as duplicates?

   • AScore of 70; flagged as a duplicate
   • BScore of 80; flagged as a duplicate
   • CScore of 90; not flagged as a duplicate
   • DScore of 90; flagged as a duplicate
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A data architect is defining survivorship rules for a customer master record that is built from three sources: CRM, billing, and support. The CRM has the most accurate phone numbers, the billing system has the most accurate addresses, and the support system has the most accurate email addresses. However, the support system's email field is often empty. The architect wants to maximize data quality while minimizing empty fields. Which survivorship rule is best?

   • AUse record-level survivorship and always take the entire record from the CRM
   • BUse the most recently updated field from any source without source priority
   • CUse a single source for all fields and manually correct the rest
   • DUse field-level survivorship with source priority per field, and add a fallback to fill empty values from other sources
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A media company is integrating customer data from a subscription system, an advertising system, and a support system. Each system uses a different identifier for customers. The data architect needs to design the MDM hub so that all three systems can exchange data without changing their internal schemas. What is the most effective approach?

   • AStore three separate customer tables in the MDM, one for each source system
   • BUse the subscription system's customer ID as the universal identifier for all systems
   • CCreate a canonical customer model in the MDM hub and map each system's identifier and attributes to it
   • DBuild direct integrations between each pair of systems to translate data on the fly
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   A data architect is consolidating customer data from two systems. After cleansing, they need to identify which records from the two systems refer to the same real-world customer. Which step in the consolidation process accomplishes this?

   • AData cleansing
   • BData matching
   • CData merging
   • DData profiling
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A multinational company manages a sales hierarchy where regional managers report to country managers, who report to a global sales director. The company frequently reorganizes its sales regions, and the data architect needs to maintain historical reporting while supporting the current structure. Which hierarchy management approach should be used?

   • AA fixed hierarchy that is updated in place whenever a reorganization occurs
   • BA single flat list of all employees with no parent-child relationships
   • CA hierarchy stored only in the source CRM system without replication to the MDM
   • DVersioned hierarchy with effective-dated parent-child relationships
   Reveal Solution Discussion Select an answer first