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

Questions 26–30

1. 26foundation · easy

   Which of the following is a key characteristic of a canonical data model?

   • AIt requires all systems to use the same database technology
   • BIt is independent of any specific source system's format
   • CIt is only used for reporting purposes
   • DIt is identical to the database schema of the primary source system
   Reveal Solution Discussion Select an answer first
2. 27foundation · easy

   A company has two source systems for customer data. The data steward wants the master record to always use the address from the CRM system, regardless of which system was updated last. Which survivorship rule should be configured?

   • AMost recent timestamp
   • BSource priority
   • CRandom selection
   • DField-level trust
   Reveal Solution Discussion Select an answer first
4. 28expert · hard · select all that apply

   A data architect is consolidating customer records from two acquisition systems. The matching process uses weighted fields and a confidence threshold. The architect wants to ensure that the consolidation process is accurate and auditable. Select all that apply: which practices should the architect implement?

   • ADefine clear survivorship rules that specify which source prevails for each field
   • BUse a low confidence threshold to maximize the number of auto-merges
   • CAllow data stewards to review and override matches below the auto-merge threshold
   • DLog the match scores and survivorship decisions for every merged record
   • ESkip data cleansing because the matching algorithm can handle dirty data
   Check answers Discussion Select an answer first
5. 29foundation · easy

   A company needs to provide a single, unified view of customer data across multiple source systems without immediately changing the source systems. They want to create a central hub that stores the best version of each record and distributes updates back to the sources. Which MDM implementation style best fits this requirement?

   • AConsolidation style
   • BRegistry style
   • CCo-existence style
   • DTransactional style
   Reveal Solution Discussion Select an answer first
6. 30foundation · easy

   A company wants to add demographic information, such as age and income, to its customer master data. This data is not available internally. Which approach should they use?

   • AData cleansing
   • BData profiling
   • CData matching
   • DExternal reference data enrichment
   Reveal Solution Discussion Select an answer first