PracticeISCFree practice exam

ISC · Information Systems and Data Management · 9 practice questions

Customer MDM After a Merger: Fix Duplicate IDs Across Systems

Master data management creates a governed customer identity and synchronizes authoritative updates across operational systems. Below: compare proposed responses to duplicate customer records after a merger.

The ruleUse an MDM hub with governed enterprise identifiers, matching and survivorship rules, and attribute-level systems of record to reconcile customer masters. Preserve source-ID mappings and synchronize authoritative updates to operational systems.

Try one first

Apex Retail has acquired ByteMart. Both companies maintain separate production OLTP customer systems that use different customer identifier schemes, and neither system contains a consistently used national ID or email field. There are many duplicate customer records across the two systems and inconsistent address/formatting conventions. Management requires a single authoritative customer identifier for consolidated reporting and analytics, and historical transactions (which reference the original source system customer IDs) must remain linkable. Operational constraints prohibit making intrusive changes to the existing OLTP systems. Which of the following is the most appropriate data-management approach to create a reliable consolidated customer master while minimizing disruption?
Hint

Focus on a solution that (1) creates a single authoritative ID for analytics, (2) preserves existing source IDs and linkages for historical transactions, and (3) avoids intrusive changes to production OLTP systems.

What should you do?

The situation

After an acquisition, Apex retains separate CRM, ERP, and billing applications. Customers have different IDs, inconsistent addresses, and no consistently populated shared email field. Historical invoices reference legacy IDs. CRM is the approved source for contact addresses; billing verifies tax status. A read-only warehouse receives nightly extracts, but operational records still conflict. Management wants an ongoing authoritative customer record without replacing the applications. Which response is best?

  1. Implement an MDM hub with enterprise IDs, stewardship, field-level authority, and operational synchronization.

    Best Use probabilistic matching and steward review to resolve identities. Retain legacy-ID mappings, apply survivorship rules using approved field owners, and distribute mastered records.

  2. Deduplicate customer records only in the warehouse during nightly ETL.

    Wrong Reports may improve, but CRM, ERP, and billing still use conflicting customer records. A read-only warehouse does not synchronize authoritative operational updates.

  3. Make CRM authoritative for every customer field and export its values.

    Wrong CRM owns contact addresses, not verified tax status. Forcing every field into one source ignores approved attribute-level authority.

  4. Clean existing duplicates once, then let each application maintain customers independently.

    Wrong The cleanup fixes current records only. Independent creation and updates can recreate duplicates without enterprise identifiers, stewardship, and ongoing governance.

  5. Synchronize records automatically without defining ownership or survivorship rules.

    Wrong Synchronization can spread conflicting values. Apex still needs rules and accountable stewards to decide which records match and which field values survive.

  6. Replace all legacy IDs and rewrite historical invoice references.

    Wrong This creates unnecessary disruption. Persistent mappings between enterprise and legacy IDs preserve historical links without rewriting every source identifier and transaction reference.

Key points

  • Remember: A clean warehouse report does not fix conflicting customer records used in daily operations.
  • Map legacy IDs to the enterprise ID so historical transactions remain linkable.
  • Use probabilistic matching when no reliable shared identifier exists; send ambiguous matches to stewards.
  • Survivorship rules select authoritative field values; one application need not own every field.

How the exam traps you

  • Deduplicate only during nightly warehouse loads. Synchronize governed master records to operational systems, not just reporting copies.
  • Make CRM authoritative for every customer field. Assign authority by attribute, preserving billing's ownership of verified tax status.
  • Clean existing duplicates once and keep local update procedures unchanged. Govern matching, creation, and updates continuously to prevent recurrence.

8 more, each from a different angle

0 of 8 answered · 0 correct

Question 2

A company keeps vendor information in separate spreadsheets maintained by accounts payable, purchasing, and receiving. Vendor names, addresses, and payment terms often differ across the files, which has led to duplicate records and inconsistent internal reports. Assuming the company wants the most direct data management improvement, which action is most appropriate?
Hint

Focus on which choice best creates one reliable source for the same data element across departments.

Question 3

Company A is migrating customer records from three legacy systems (CRM, billing, and shipping) into a new ERP. About 15% of customers have conflicting addresses across systems and 8% of records lack email addresses required by the ERP's matching tool. There are no data-steward roles or documented governance rules, and management wants to minimize migration effort. Considering correct data-management practice, which of the following best describes how to prepare the customer data before migration and what governance action should accompany it?
Hint

Decide whether the inconsistencies should be corrected before records enter the ERP and who should own ongoing data quality.

Question 4

A company stores customer address data in separate sales, shipping, and billing systems. Each department updates its own records, and customers are increasingly receiving invoices at old addresses. Assume the company wants to reduce these errors on an ongoing basis, not just detect them after they occur. Which response is most appropriate?
Hint

Focus on which option prevents duplicate or conflicting versions of the same data from being maintained in different places.

Question 5

Apex Co. is revising its data-management policy to reduce storage costs while maintaining data quality and compliance. Its ERP contains three datasets: (1) Customer master records (name, address, tax ID, primary contact; updated occasionally), (2) Sales transaction history (order-level detail for the past 10 years; used for tax reporting and financial close), and (3) System audit logs (detailed user activity, currently retained for 90 days). Which of the following is the MOST appropriate overall treatment for these datasets?
Hint

Classify each dataset by role and lifecycle (master/reference vs transactional vs audit) and choose governance, archival, and retention controls appropriate to each category.

Question 6

A company stores customer information in separate sales, billing, and support systems. As a result, the same customer may appear with different names or addresses in different applications, causing duplicate records and inconsistent management reports. Management wants one reliable version of key customer data and clear responsibility for approving changes. Which action is best?
Hint

Focus on the control that improves data quality and consistency across systems, not the ones that mainly protect or recover data.

Question 7

Company Alpha uses three separate systems for order entry, billing, and collections. Each system maintains its own customer master, producing inconsistent customer IDs, addresses, and duplicate customer records that have caused duplicate invoices, missed collections, and periodic revenue-recognition errors. Management asks the controller to mandate a single change that will most effectively reduce the ongoing risk of revenue misstatement and operational inefficiency caused by inconsistent customer master data. Which single change should the controller require?
Hint

Think preventive and enterprise-wide: which single change would create one authoritative customer record across all systems rather than just detecting mismatches or limiting who can change local records?

Question 8

During Year 1, an entity discovered that its sales, billing, and collections departments each maintain a separate customer record file. Customer addresses and credit limits often conflict across the files, leading to invoicing errors. Assume management wants to improve data accuracy at the source rather than merely detect errors later. Which response is most appropriate?
Hint

Focus on the control that fixes the source of the inconsistency, not a control that only preserves or later compares bad data.

Question 9

A mid-sized financial services firm uses three operational systems (CRM, loans, payments) that each maintain customer records. An audit found 20% of consolidated customer records have inconsistent core fields (e.g., different DOB or address across systems) and 15% are missing taxpayer ID information. Regulatory reports are produced from a consolidated data warehouse. The firm has encryption at rest, role-based access controls, and a data stewardship group, but no Master Data Management (MDM), no enterprise-wide unique customer identifier, no documented data lineage or metadata catalog, and performs data-quality checks only during batch ETL into the warehouse (not at the source). Which of the following is the best next step to most effectively reduce duplicates and inconsistencies and improve reliability for reporting?
Hint

Ask where the inconsistencies originate and when they are detected; prioritize preventive, source-level fixes that establish one authoritative customer record.

Drill all 170 Data management questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

Common questions

Why isn't a data warehouse enough to fix duplicate customer records?

Apex's read-only warehouse can reconcile reporting copies but cannot correct operational records. MDM governs customer identity and distributes authoritative updates to the applications.

Does a golden customer record require one system to own every field?

No. Apex can use CRM as the authority for contact addresses and billing as the authority for verified tax status. Survivorship rules determine which values populate the golden record.

Should MDM replace legacy customer IDs after a merger?

Not necessarily. Apex can retain legacy IDs and map them to an enterprise ID, preserving historical transaction links without replacing the source applications.

Watch it solved

A full CPA ISC task-based simulation on Data management, worked step by step.

Data Quality Defects & ETL Reconciliation | CPA ISC Simulation (TBS) on YouTube

Practice ISC like the real exam

The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.

Open the free simulator →

More on Data management

All Data management practice →

Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.