ISC · Information Systems and Data Management · 7 practice questions
MDM Address Changes: When Is Steward Approval Required?
A non-authoritative source cannot change the golden record without the required data-steward authorization. Below, compare AlphaCo's same address submission with only the stewardship case disposition changed.
Try one first
Hint
Identify that the mailing address is master data and apply the governance rule about how changes from non-authoritative sources must be handled, who must validate and authorize before the golden record is changed.
Answer C. Because the address change originated from a non-authoritative source, governance requires data-steward review before modifying the golden record. Opening a stewardship case preserves auditability, lets the steward validate the supporting document, and ensures coordinated updates with the authoritative Billing system and downstream propagation, avoiding unauthorized or conflicting updates.
Why not A: Tempting because the Web Portal includes supporting documentation and shows the new address, but it violates governance: lower-tier sources may not automatically overwrite the golden record without data-steward authorization and would risk introducing unverified authoritative changes.
Why not B: Tempting because Billing is authoritative and the nightly sync may restore the Billing value, but passively ignoring a customer-submitted change (with apparent evidence) breaches policy that requires steward review of non-authoritative requests rather than doing nothing.
Why not D: Tempting because changing the authoritative source would align systems, but directing manual changes in Billing bypasses MDM stewardship and governance controls and undermines the centralized audit and coordination role of MDM.
Side by side
| Pending review | Approved after validation | Rejected after review | |
|---|---|---|---|
| Same AlphaCo submission | Portal address change with a scanned utility bill that appears valid. | Portal address change with a scanned utility bill that appears valid. | Portal address change with a scanned utility bill that appears valid. |
| Same mailing-address hierarchy | Billing > CRM > Web Portal. | Billing > CRM > Web Portal. | Billing > CRM > Web Portal. |
| Same source values before action | Portal shows the new address; Billing and CRM show the old address. | Portal shows the new address; Billing and CRM show the old address. | Portal shows the new address; Billing and CRM show the old address. |
| Same nightly sync | Billing's authoritative feed overwrites lower-tier address values. | Billing's authoritative feed overwrites lower-tier address values. | Billing's authoritative feed overwrites lower-tier address values. |
| Only changed fact: case disposition | Review and authorization are pending. | The steward validated the evidence and authorized the change. | The steward reviewed the evidence and rejected the change. |
| Immediate action | Verify the evidence and obtain authorization before modifying the golden record. | Update the golden record and coordinate Billing and CRM corrections. | Do not apply the submitted address; document the rejection. |
| Golden-record treatment | No change while authorization is pending. | Apply the authorized new address. | Do not apply the rejected address. |
| Billing and CRM coordination | Arrange corrections only if the steward authorizes the change. | Coordinate corrections so Billing's nightly feed preserves the approved address. | Do not propagate the rejected address to Billing or CRM. |
| Stewardship audit trail | Record submitted evidence and pending status; record validation and authorization or rejection before any golden-record modification. | Record submitted evidence, successful validation, and authorization before updating the golden record. | Record submitted evidence, validation result, and rejection; make no golden-record change. |
Key points
- Remember: Supporting evidence starts the review; steward authorization permits the golden-record change.
- Billing is AlphaCo's authoritative source for mailing addresses.
- Record the evidence, validation result, and authorization or rejection in the stewardship case before any golden-record modification.
How the exam traps you
- Automatically accept the Portal address because a utility bill is attached. Verify the evidence and obtain steward authorization first.
- Leave a pending submission unresolved because Billing will sync tonight. Complete the stewardship review instead of relying on the sync.
- Update only the golden record after approval. Coordinate Billing and CRM corrections so the nightly sync does not restore the old address.
Question 2
Hint
Which first step establishes accountability and measures the scope and causes of the problems before choosing technical controls or consolidation?
Answer A. First establish governance and business ownership so responsibilities and decision rights are clear. Data profiling and a data-quality assessment quantify the issues and identify root causes, which enables prioritized remediation. Technical consolidation or controls are far more likely to succeed after standards, stewardship, and a remediation plan are in place.
Why not B: Attractive as a technical control, but locking edits centralizes authority in IT and does not resolve existing duplicates or inconsistent formats created outside the ERP; referential constraints do not replace business-defined standards or stewardship.
Why not C: Tempting because centralizing in MDM promises a single source of truth, but migrating spreadsheets before profiling and cleansing typically imports duplicates and inconsistent data at scale; without governance and standards the same errors persist and effort is wasted.
Why not D: Feels decisive, but an abrupt ban and manual change process will disrupt operations and encourage workarounds; without assigned owners, cleansing, and agreed standards the underlying quality problems remain.
Question 3
Hint
Decide whether the obstacle prevents deciding which source value is the authoritative 'truth' (an organizational/governance issue) or merely makes matching, ingestion, or freshness technically harder.
Answer C. MDM can only produce consistent, accurate enterprise golden records when stakeholders agree on attribute definitions, validation logic, and which source is authoritative. Those governance decisions determine how conflicting values are reconciled across systems. Technical tools (ETL, matching, and identifier generation) support merging and matching, but they cannot substitute for the organizational rules needed to establish the enterprise 'truth.'
Why not A: A persistent enterprise ID makes deterministic matching simpler, so this is tempting, but modern MDM approaches commonly use probabilistic/fuzzy matching and can assign a persistent enterprise identifier after reconciliation. Lacking a native shared ID is a technical obstacle, not the core blocker when governance exists to resolve conflicts.
Why not B: Unstructured data complicates ingestion and matching and can reduce accuracy, which makes this a plausible concern. However, OCR, NLP, and data-cleaning processes can convert many attributes into structured form; this is primarily a data-preparation limitation rather than the fundamental governance issue that prevents deciding authoritative values.
Why not D: High-velocity updates pose operational and synchronization challenges (favoring streaming or change-data-capture solutions), but they do not inherently prevent establishing authoritative master attributes. Freshness is an operational concern, whereas lacking governance prevents consistent reconciliation of conflicting values.
Question 4
Hint
Focus on whether the problem is definitions, detection, retention, or deciding which shared customer record should be treated as the enterprise source of truth.
Answer C. The core problem is that the enterprise lacks an authoritative way to determine which customer record should prevail across systems. Different source IDs combined with last-loaded overwrites indicate missing master data governance practices, record matching, clear data ownership, and survivorship rules. Without those governance rules, monitoring or metadata controls can detect inconsistencies but cannot reliably resolve them across reports.
Why not A: This is tempting because lineage and definitions matter when reports disagree. However, the stem already states the reporting glossary and ETL mappings are documented, so lack of metadata is not the primary failure. The fundamental issue is the absence of authoritative record matching and survivorship rules.
Why not B: Duplicate detection and exception reporting are useful controls, but they are downstream. Monitoring can surface the problem but does not establish which system or record should be the enterprise source of truth. The root cause is missing master data governance.
Why not D: Archiving older records may reduce clutter but does not address the fact that the same current customer exists under different IDs and that shared fields are overwritten without survivorship rules. The conflict concerns authoritative record management, not retention timing.
Question 5
Hint
Focus on whether the weakness is mainly about speed, input validation, approval, or ownership of specific data attributes across systems.
Answer B. The root problem is design and ownership of master data rather than synchronization speed or isolated input errors. Assigning authoritative sources at the attribute level, standardizing matching/merge rules, and implementing attribute-level survivorship prevents nonauthoritative systems from overwriting the wrong fields, stops blank-field regressions, and reduces duplicates without replacing applications.
Why not A: Speeding up synchronization may reduce the window for conflicts but does not change the underlying rule that a full record can overwrite authoritative attributes. Real-time updates simply propagate the same flawed "last update wins" logic faster, so incorrect attributes can still become authoritative.
Why not C: Validation edits address local data-quality symptoms but not the cross-system ownership or matching inconsistencies. They cannot by themselves ensure a consistent source-of-record or prevent one system's record from overwriting attributes owned by another system.
Why not D: Centralizing approvals in ERP may be heavy-handed and impractical because different attributes logically originate in different systems (CRM, ERP, e-commerce). Routing all changes through ERP doesn't standardize matching or survivorship and can create unnecessary process bottlenecks without fixing duplicate-record or overwrite issues.
Question 6
Hint
Distinguish who sets policy (owners/governance), who operates and maintains data quality (stewards), and who handles technical infrastructure (IT).
Answer C. Data stewards are responsible for the operational management of data quality and standards, they define data definitions, naming conventions, and validation rules and perform data cleansing tasks such as deduplication and correcting inconsistent records. Policy-level decisions like retention and formal classification are typically owned by the data owner or governance/compliance teams, while technical infrastructure tasks are handled by IT operations.
Why not A: This is tempting because retention affects the data lifecycle, but approving retention schedules and legal-hold procedures is a policy-level responsibility normally held by the data owner, governance, or legal functions rather than the day-to-day data steward.
Why not B: This describes technical infrastructure work. While stewards care about data availability and quality, configuring backups and performing restores are operational IT responsibilities, not typical business-focused steward tasks.
Why not D: Stewards may help advise on data definitions for classification, but formal role-based access policies and regulatory classification are usually owned by the data owner, governance, or security/compliance teams in coordination with legal.
Question 7
Hint
Decide whether the needed solution must produce and sustain a single enterprise customer identifier and governance across systems, or whether it merely centralizes or periodically cleans reporting data.
Answer D. The core issue is inconsistent customer identity across multiple operational systems. An enterprise MDM program creates a persistent golden record and enterprise identifier and pairs technical fixes (profiling, matching, standardization, automated merge rules) with governance so identities are reconciled and maintained. Starting with a targeted pilot fits the limited budget while demonstrating value before full rollout.
Why not A: Batch deduplication tempts by appearing lower-cost and operationally simple, but it is reactive: duplicates will reappear as new transactions enter source systems and reconciliation is delayed. Without an enterprise identifier and governance the approach won't sustain a single maintained customer identity or support real-time operational needs.
Why not B: This is tempting because a data lake centralizes raw data quickly and cheaply, but it preserves inconsistent IDs and defers identity resolution to analysts at query time. That leads to repeated reconciliation work, inconsistent results across teams, and no maintained enterprise customer identifier to prevent recurring cross-system errors.
Why not C: This appears attractive because referential integrity enforces consistency within reporting, but it presumes or relies on mapping that must be maintained and does not fix upstream ID capture or provide governance. It centralizes reporting consistency only and does not produce a persistent enterprise identifier across operational systems.
Common questions
Can a utility bill let a Web Portal address override the MDM golden record?
Not automatically. AlphaCo requires the data steward to validate the evidence and authorize the change before modifying the golden record.
What happens after a data steward approves an address change?
Update the golden record and coordinate corrections to Billing and CRM. Billing's nightly feed could otherwise overwrite the approved address with the old value.
What happens if a data steward rejects an address change?
Do not apply the submitted address. Record the reviewed evidence, validation result, and rejection in the stewardship case.
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
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.