Master Data Management

CIMP · 50 questions

• A city IT lead claims every table in the permitting database is master data because staff reuse those tables often. Which distinction should the information manager make?
• Permit, licensing, and inspection systems each store slightly different spellings and tax IDs for the same contractor companies, causing wrong notifications and duplicate vendor payments. What problem does this primarily motivate?
• Multiple municipal systems need read access to a trusted golden customer record, while local updates are reconciled centrally before republishing. Which architecture pattern best fits this requirement at a conceptual level?
• A county proposes an MDM style that only indexes pointers to resident records in source systems and does not materialize a composed set of attributes. How does this differ from a consolidation approach?
• Utility billing, CRM, and field-service apps will keep local customer copies, while an MDM layer synchronizes a defined set of critical shared attributes. Which pattern is being applied?
• Two resident rows show 'Jon Smith' and 'John Smith' at the same address with the same phone number. What should matching capability primarily accomplish?
• Before comparing parcel and mailing addresses for resident matching, the team breaks street lines into house number, street name, and unit. Why is that step important?
• CRM shows one email for a taxpayer while billing shows a different email for the same matched person. What should survivorship design do?
• An aggressive auto-merge collapses two different residents who share a common name into one golden person, mixing their benefit histories. What risk does this illustrate, and what control helps?
• Match rules are so strict that true duplicate customer rows never merge, leaving fragmented service history across systems. What does this situation represent?
• An MDM platform is live, yet conflict queues stall because no one is accountable for approving match and survivorship decisions. What role is missing?
• A municipality wants MDM for every entity at once—parties, assets, vendors, employees, and more—before any domain is mastered. What sequencing guidance fits best?
• A project team labels permit-type code lists as 'master data' in the same sense as contractor and parcel entities. What distinction should be clarified?
• After a trusted golden resident record is published to the call center, agents resolve more issues on the first contact without hunting across systems. What does this outcome demonstrate?
• For the same property party, the assessor system is trusted for legal owner name while CRM is trusted for contact preference. What survivorship principle applies?
• A service desk needs to recognize returning residents during the call, but party matching only runs in a weekly batch. What architectural concern does this raise?
• Before writing party match rules, analysts profile name fields and find heavy nickname use, missing middle initials, and inconsistent suffixes. Why does that profiling matter for MDM?
• A city plans multi-domain MDM covering party, location, and asset but only designs isolated golden records with no links among them. What is missing?
• Fraud and audit teams need prior resident addresses after a move updates the golden record. What MDM design requirement should be included?
• Architects debate issuing a new surviving enterprise party ID versus keeping each source key and maintaining a crosswalk. What is the sound guidance?
• Matching discussions contrast a stable business license number with an internal surrogate database key that resets when systems are rebuilt. What principle should guide the team?
• A utility proposes 'householding' accounts that share a service address for marketing and outreach, separate from legal person entities used for contracts. What clarification is needed?
• Clerical staff can propose resident merges, stewards must approve them, and only then does the MDM system execute the merge. What does this workflow emphasize?
• The MDM team plans to call an external address-validation service to standardize locations before matching. What implementation stance is appropriate?
• Leadership funds an MDM product install with no business workshops on match or survivorship rules, treating the effort as a pure IT deployment. What outcome is most likely?
• A city MDM program wants operational KPIs that show whether matching and golden records are improving. Which metric set best fits that goal?
• Canonical model debates keep delaying the first MDM go-live across every enterprise entity type. What delivery approach should the program favor?
• Clerks enter free-text company names that mix legal names, trade names, and noise tokens, so organization matching fails. What should MDM implement first for reliable matching?
• Two golden records appear for the same branch because legacy regional codes differ. How should matching be redesigned?
• Stewards merge two parties and later prove the merge was wrong. What capability must the MDM design provide?
• A municipality needs a trusted catalog of fees and services used across permitting and billing. How should MDM thinking apply?
• Emergency routing depends on the location master, and wrong geocodes have delayed responses. What should the program do?
• Downstream systems need master changes within minutes, while a reporting warehouse can wait overnight. How should master distribution be designed?
• A billing app silently overwrites mastered address attributes with local edits. What consumption rule should governance enforce?
• An initial MDM load floods the match queue with years of historical duplicates. What should the implementation plan include?
• Consolidating citizen personal data into a golden hub concentrates privacy risk. What control change is most appropriate?
• Leadership wants to buy an MDM platform before domains, match rules, or success metrics are defined. What sequencing should the candidate recommend?
• Business licenses must attach to legal entities while inspections occur at branch locations. What MDM modeling need does this create?
• Leadership proposes timing stewards only on how fast they clear match suspects. What measurement approach is more sound?
• After merges, legacy systems still need their original keys to keep integrations working. What identifier practice should MDM retain?
• A peer city shares fuzzy-match thresholds that look convenient to copy unchanged. What should the MDM team do before production use?
• Teams still treat local spreadsheets as the real customer list after the hub goes live. What adoption action best addresses the bypass?
• Only a shared core of party attributes should be mastered, while volatile order details stay in transactional systems. Which retrieval pattern fits?
• The data governance council is standing up MDM for the party domain. What ownership action should it take?
• Citizen names in a multilingual community are often spelled inconsistently across systems. Which matching technique belongs in the toolkit?
• Survivorship must keep the oldest account-open date but the newest verified email when records merge. What rule design is required?
• Retired master records are subject to retention schedules and legal holds. How should deletion be handled?
• Match thresholds are about to freeze for production. What testing step should precede that decision?
• Leaders ask how to prove address mastering helped residents. Which KPI best shows outside-in outcome value?
• After the first cleanse, sponsors treat MDM as finished. How should the roadmap be framed instead?