Free DAMA CDMP Quality Practice Questions: Master Reference and Warehouse Quality

Topic snapshot

Sample questions

These are original IT Mastery practice questions aligned to this topic area. They are not official exam questions, copied live-exam content, or exam dumps. Use them for self-assessment, scope review, and deciding what to drill next.

Question 1

Topic: Master Reference Integration and Warehouse Quality

Two business units submit monthly sales data to the enterprise warehouse. Profiling shows that both use valid local product category codes, but the same codes roll up to different reporting categories in enterprise dashboards. Executives need comparable cross-unit reporting without removing legitimate local operational codes. What is the best action?

Options:

• A. Establish a governed enterprise reference mapping

• B. Delete nonmatching local category codes

• C. Raise the completeness threshold for category fields

• D. Recalculate dashboard totals after each load

Best answer: A

Explanation: Inconsistent reference values across business units are a reference data quality and governance problem, not simply a warehouse calculation problem. The local codes may be valid for operations, but enterprise reporting needs a shared interpretation of how those codes map to common categories. A governed enterprise reference mapping, approved by data stewards and maintained as controlled reference data, supports both local use and comparable reporting. It also creates a sustainable control point for future changes.

Deleting local codes would damage operational meaning, while recalculating dashboards only repeats the incompatible rollups more efficiently. The key is to standardize the enterprise classification relationship, not force every source to abandon legitimate local values.

• Deleting local codes fails because the scenario says the local codes are legitimate for operational use.
• Completeness threshold targets missing values, but the defect is inconsistent interpretation of present values.
• Dashboard recalculation addresses processing timing, not the conflicting reference-data mappings.

Question 2

Topic: Master Reference Integration and Warehouse Quality

A finance BI dashboard is used each morning for margin decisions and supplier negotiations. Profiling shows that refunds arriving after the nightly warehouse load are applied to the original order date, causing net revenue for the most recent 3 business days to be overstated by 8% to 12%. Product and customer reference data pass validity checks. The source team can change the refund feed in 6 weeks, but executives need the dashboard to remain usable with clear trust signals now. Which quality control is the best decision?

Options:

• A. Cleanse the last quarter of refund transactions once

• B. Ask users to manually exclude the latest 3 days

• C. Increase the warehouse load frequency for all sales feeds

• D. Add a reconciliation rule with threshold-based BI certification status

Best answer: D

Explanation: BI decision trust depends on making known analytical data quality risk visible and controlled at the point of use. The defect is not reference-data validity; it is a timing and reconciliation problem between orders and late-arriving refunds. A warehouse/BI quality rule should compare expected refunds to posted net revenue by business date, apply an approved threshold, and show certification or warning status for affected reporting periods. This lets executives distinguish trusted periods from provisional periods while remediation occurs at the source. The key takeaway is to pair measurement with governed trust signals, not rely on hidden cleanup or user workarounds.

• One-time cleansing may correct past records but does not prevent or expose the recurring late-arrival defect.
• More frequent loading does not address refund-to-order-date reconciliation and may simply refresh inaccurate provisional results faster.
• Manual exclusion shifts quality control to dashboard users and weakens consistent governance over decision trust.

Question 3

Topic: Master Reference Integration and Warehouse Quality

A bank’s customer master feeds a warehouse report that aggregates total credit exposure by corporate group. Profiling shows customer identifiers are valid and mostly complete, but 9% of subsidiary records are linked to inactive or outdated parent companies after mergers. Relationship changes are currently submitted by regional teams without a common approval rule, and Finance needs auditable group-level reporting each month. Which quality control best addresses the issue?

Options:

• A. Monthly manual overrides in the warehouse report

• B. A one-time duplicate merge of subsidiary customer records

• C. Format validation on customer identifier fields

• D. Governed hierarchy-change workflow with approved relationship rules

Best answer: D

Explanation: The strongest control targets master data hierarchy quality, not just record format or downstream presentation. The identifiers are already valid and mostly complete, while the business impact comes from incorrect parent-child relationships used for credit exposure aggregation. A governed hierarchy-change workflow should define who may request and approve relationship changes, apply common match and relationship rules, capture effective dates and lineage, and monitor exceptions such as inactive parents. This supports sustained quality and auditability for Finance. Downstream reporting fixes may hide the symptom, but they do not control the master relationship data that multiple consumers rely on.

• Duplicate merge may help uniqueness, but the stated problem is outdated corporate relationships, not duplicate subsidiary records.
• Identifier validation checks technical validity, but valid IDs can still point to the wrong parent in a hierarchy.
• Warehouse overrides may patch monthly reports, but they bypass governed master data maintenance and weaken auditability.

Question 4

Topic: Master Reference Integration and Warehouse Quality

A retailer profiles integrated customer and product data. The same review finds duplicate customer records for the same legal entity, product rows with category code ELEC-99 that is not in the approved category list, and a category hierarchy where TABLET rolls up to both Electronics and Accessories. Which classification best separates the master data quality issue from the reference data code-set issue?

Options:

• A. All findings are master data because they appear in customer or product records.

• B. Duplicate customers and invalid codes are master data; roll-ups are only metadata.

• C. Duplicate customers are master data; invalid category codes and roll-ups are reference data.

• D. Invalid codes are source-entry errors; duplicates and roll-ups are reference data.

Best answer: C

Explanation: Master data represents core business entities such as customers, products, suppliers, or locations. A duplicate customer record is a master data quality issue because it concerns whether one real-world entity is represented once and correctly. Reference data defines controlled values and classifications used by other data, such as category codes, status codes, country codes, and their allowed hierarchies. An invalid category code and conflicting category roll-up are reference data code-set or hierarchy issues, even when the affected field is stored on a product master record. The decisive distinction is the thing being corrected: entity identity and survivorship for master data, versus approved values and controlled relationships for reference data.

• Record location trap fails because a code stored in a master record can still be governed as reference data.
• Metadata-only trap fails because a controlled category roll-up is part of reference data governance, not merely descriptive metadata.
• Source-entry trap fails because invalid entered values may reveal a missing or poorly governed approved code set.

Question 5

Topic: Master Reference Integration and Warehouse Quality

A health insurer integrates provider master data into its warehouse. Profiling shows that 6% of active provider records share the same national provider identifier but have different internal provider IDs because regional onboarding can create local records before central match review. Claims processing uses the national identifier, so payments are not delayed. The provider performance dashboard groups by internal provider ID and feeds contract negotiation analytics. Which quality decision best describes the main impact?

Options:

• A. Stale reference data causes late dashboard refreshes.

• B. Invalid claim codes prevent accurate payment adjudication.

• C. Duplicate master records fragment provider analytics and understate provider-level totals.

• D. Incomplete provider records block operational claims processing.

Best answer: C

Explanation: The visible defect is a master data uniqueness problem: the same real-world provider is represented by multiple internal provider records. Because operational claims processing uses the national identifier and is not delayed, the primary impact is not payment execution. The downstream warehouse groups by internal provider ID, so measures such as spend, performance, and volume are split across duplicates. That can make provider-level totals appear lower or inconsistent, which directly affects contract negotiation analytics. The best quality decision connects the duplicate-record evidence to the analytic impact, not to unrelated validity, completeness, or timeliness issues.

• Claim-code validity does not fit because the defect concerns provider identifiers, not diagnosis, procedure, or claim code values.
• Operational blockage is contradicted by the fact that claims processing uses the national identifier and payments are not delayed.
• Refresh timeliness is not supported because the issue is record identity fragmentation, not delayed warehouse loading or stale reference values.

Question 6

Topic: Master Reference Integration and Warehouse Quality

A customer MDM hub supplies standardized customer records to a data warehouse. Several source systems have started sending new customer segment codes that are not in the enterprise reference list, causing inconsistent segment reporting. Business users want the data quality team to prevent recurrence, not just repair this month’s warehouse load. What is the best action?

Options:

• A. Route new segment codes through reference data stewardship and governance approval before publication

• B. Map all unknown segment codes to Other in the warehouse load

• C. Let each source system maintain its own segment list

• D. Add a scorecard metric showing the count of unknown segment codes

Best answer: A

Explanation: Reference data quality depends on controlled definition, approval, publication, and use of shared code sets. Because customer segment codes drive enterprise reporting across MDM and the warehouse, the recurring defect should be handled where the reference values are governed, not only where the defect appears. Stewardship review confirms business meaning, governance approval authorizes changes to the shared list, and publication makes the approved values available to MDM, integration, and downstream validation controls. Warehouse cleansing may be needed for current exceptions, but it should not become the primary control for creating or legitimizing new enterprise segment codes. The durable fix is to prevent unapproved values from entering shared data flows.

• Warehouse mapping hides the defect and can distort reporting when unknown values have distinct business meanings.
• Local code lists increase inconsistency because each source can define segments differently.
• Scorecard counts measure the issue but do not approve values or prevent recurrence.

Question 7

Topic: Master Reference Integration and Warehouse Quality

A customer analytics warehouse receives nightly feeds from CRM and billing. The loads complete with no rejected rows, and profiling shows customer_status contains only valid codes in both sources. However, CRM uses inactive to mean “no login in 90 days,” while billing uses inactive to mean “no billable subscription.” A churn dashboard now suppresses some active subscribers from retention campaigns. There is no approved enterprise definition for status, and schema changes are frozen this quarter. What is the best quality decision?

Options:

• A. Reject all records where source systems disagree on status

• B. Keep the warehouse unchanged and add a dashboard footnote

• C. Rerun the nightly loads after increasing batch validation logging

• D. Approve a governed status definition and mapping, then update transformation rules

Best answer: D

Explanation: Technically successful movement can still create poor data quality when values have different business meanings. Here, validity checks pass because the codes are allowed, but the downstream warehouse combines incompatible definitions of inactive. The sustainable remediation is to establish the business definition and source-to-target mapping through the appropriate data owners or stewards, then implement that approved rule in the integration layer within the current schema constraints. Monitoring should then verify that the mapped result remains fit for retention campaign use. More logging or reloading addresses transport reliability, not semantic quality. Rejecting disagreements may create unnecessary data loss without resolving the meaning problem.

• More logging confirms processing behavior but does not reconcile the conflicting meanings of the same code.
• Rejecting disagreements treats semantic variation as a row-level defect and can remove usable records without an approved rule.
• Dashboard footnotes disclose ambiguity but leave the warehouse metric unfit for operational campaign decisions.

Question 8

Topic: Master Reference Integration and Warehouse Quality

A customer master feed is loaded into the enterprise warehouse through a source-to-target mapping. Profiling shows that all incoming customer_status values are populated and use valid source codes. The mapping currently converts source code S (suspended) to target code I (inactive) because the target reference list did not include suspended when the interface was built. Sales reporting now undercounts suspended customers as inactive. Which data quality dimension is most affected?

Options:

• A. Accuracy

• B. Uniqueness

• C. Timeliness

• D. Completeness

Best answer: A

Explanation: Accuracy concerns whether data correctly represents the real-world fact or approved business meaning. In this mapping problem, the source value is present and valid, but the target value changes the meaning from suspended to inactive. The warehouse therefore contains a status that is syntactically acceptable but factually wrong for affected customers. Because downstream reporting uses that status for customer counts, the business impact comes from incorrect representation, not from missing, late, or duplicate records. A reference data update and mapping correction may be needed, but the dimension most directly affected is accuracy.

• Completeness does not fit because profiling shows the status field is populated in the incoming feed.
• Timeliness does not fit because no delay, stale load, or missed update window is described.
• Uniqueness does not fit because the issue is not duplicate customer records or duplicate identifiers.

Question 9

Topic: Master Reference Integration and Warehouse Quality

A warehouse loads order_status from ERP and e-commerce systems into a conformed status dimension. Profiling shows all incoming codes are valid, and nightly source-to-target row counts reconcile. Business users report that the certified “open orders” metric is overstated.

Which action best addresses the integration-quality defect?

Options:

• A. Review the source-to-target status mapping at integration design

• B. Increase nightly record-count reconciliation frequency

• C. Add stricter valid-code validation before warehouse loading

• D. Capture only table-level lineage after warehouse loading

Best answer: A

Explanation: Integration quality depends on preserving business meaning as data moves between systems. Here, both sources use a valid code P, and row counts reconcile, but the same code has different meanings in different source contexts. The failure occurs in the source-to-target mapping that conformed both values to Pending. A mapping review at the integration design or transformation point should compare source semantics, business definitions, and target dimension values before the warehouse metric is certified.

Validation can confirm allowed codes, reconciliation can confirm completeness of movement, and lineage can show where data came from. None of those alone resolves a semantic transformation error. The key distinction is that technically valid data can still be unfit for purpose when integration mapping changes its meaning.

• Valid-code checks fail to catch the problem because both P values are legitimate in their own source systems.
• Count reconciliation confirms movement completeness, not whether source meanings were transformed correctly.
• Table-level lineage is too coarse to prevent or correct the code-level semantic mismatch.

Question 10

Topic: Master Reference Integration and Warehouse Quality

A retailer finds that customer duplicates are being removed separately in CRM, billing, and the data warehouse, but new duplicates reappear each month. The same business unit also maintains a local spreadsheet of industry codes that conflicts with reporting standards. Leadership wants consistent customer and industry data across applications and analytics. Which action best fits the situation?

Options:

• A. Ask report developers to hide duplicate rows in dashboards

• B. Establish governed master and reference data quality management

• C. Run a one-time duplicate removal in the data warehouse

• D. Let each application owner clean its local customer list

Best answer: B

Explanation: Master and reference data quality management is needed when shared entities and shared code sets must be consistent across multiple systems. Customer is master data because the same business entity is used by CRM, billing, and analytics. Industry codes are reference data because they are controlled value sets used for classification. The appropriate response is not just cleansing records after they arrive downstream; it requires stewardship, agreed definitions, match and survivorship rules, approved code values, lineage-aware integration, and monitoring to prevent recurrence. One-time cleanup can improve a dataset temporarily, but it does not establish authority or controls for shared data. Local list maintenance also fails when different areas need a common enterprise view.

• Warehouse-only cleansing treats symptoms after integration and does not prevent source-system duplicates from recurring.
• Local cleanup may improve one application but preserves conflicting definitions and code sets across the enterprise.
• Dashboard suppression masks visible defects without resolving identifiers, reference values, or stewardship accountability.

Continue in the web app

Use IT Mastery for interactive DAMA CDMP Data Quality Specialist practice with mixed sets, timed mocks, topic drills, explanations, and progress tracking.

Try DAMA CDMP Data Quality Specialist on Web

Related focused pages

• Free DAMA CDMP Data Quality Specialist Full-Length Practice Exam
• Data Quality Foundations and Business Fitness
• Quality Strategy Business Case and Prioritization
• Profiling Discovery and Assessment
• Quality Rules Standards and Requirements
• Root Cause Analysis and Remediation
• Monitoring Scorecards and Measurement
• Quality Governance Roles and Stewardship
• Metadata Lineage and Quality Evidence
• Quality in Data Lifecycle and Operations
• Quality Maturity and Continuous Improvement
• Specialist Cross-Discipline Judgment