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

Questions 6–10

1. 6application · medium

   A manufacturing company manages a product hierarchy with categories, subcategories, and individual products. The marketing team wants to report on sales at each level, and the finance team needs to see the same hierarchy with different cost attributes. The data architect needs to support both views without duplicating the hierarchy. Which approach should be used?

   • ACreate two separate hierarchies, one for marketing and one for finance
   • BMaintain a single canonical hierarchy and use separate attribute sets or views for marketing and finance
   • CStore the hierarchy only in the marketing system and share it with finance via email
   • DFlatten the hierarchy into a single-level list of products
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   During a customer data consolidation project, the same customer appears in both the CRM and the billing system. The CRM record has the most recently updated phone number, while the billing system has the most recently updated billing address. The data architect needs to define a survivorship rule that produces the most complete and current master record. Which approach best meets this requirement?

   • ASource-priority survivorship: always prefer the CRM record for all fields because CRM is considered the primary system
   • BRecord-level survivorship: take the entire record from the system with the most recent overall update timestamp
   • CField-level survivorship: take the phone number from CRM and the address from billing based on last-updated timestamps per field
   • DMerge with manual review: combine all fields but flag conflicts for a data steward to resolve later
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   Why is versioning important in hierarchy management?

   • AIt ensures the hierarchy is always up-to-date
   • BIt reduces the number of hierarchy levels
   • CIt eliminates the need for parent-child relationships
   • DIt allows tracking changes to the hierarchy over time
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   A data architect is designing an MDM solution for a non-profit that manages donor records. The organization wants to enrich donor data with external wealth indicators, but the external dataset uses a different postal code format than the internal data. The architect must ensure that enrichment is accurate without over-matching. Which approach is most appropriate?

   • AUse a fuzzy match on the donor's name only, ignoring postal codes
   • BAppend all external records to the MDM without matching
   • CMatch on the raw postal code values without standardization
   • DStandardize postal codes in the canonical model, then match on the standardized value with a confidence threshold
   Reveal Solution Discussion Select an answer first
6. 10foundation · easy

   During data consolidation, a data steward notices that the same customer appears with slightly different spellings (e.g., 'Jon Smith' vs. 'John Smith') in two source systems. Which step in the harmonization process directly addresses this issue?

   • AData cleansing
   • BData merging
   • CData profiling
   • DData matching
   Reveal Solution Discussion Select an answer first