Free DAMA CDMP Quality Practice Questions: Quality Governance Roles and Stewardship

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: Quality Governance Roles and Stewardship

A customer data domain has named business data stewards, but duplicate customer records continue to affect credit exposure reporting. Profiling shows a 9% duplicate rate against an approved uniqueness rule, and the issue log shows repeated closure delays because stewards cannot obtain source-system changes from Sales Operations and have only 2 hours per month allocated. What is the best quality decision?

Options:

• A. Escalate to governance to confirm authority, ownership, and stewardship capacity

• B. Ask IT to run monthly deduplication jobs before reporting

• C. Keep the issue open and request more profiling evidence

• D. Lower the duplicate threshold until stewards can respond faster

Best answer: A

Explanation: Assigned stewardship is not enough when stewards lack authority, business engagement, or capacity. DAMA-aligned data quality practice treats stewards as part of a governance operating model: they need clear decision rights, accountable business participation, and time to manage rules, issues, and remediation. The facts show an approved rule, measured duplicate rate, business impact, and repeated delays caused by inability to secure Sales Operations changes. The best action is to escalate the operating-model gap so governance can confirm ownership, authority, and resourcing for source-process remediation. Downstream cleansing may reduce symptoms, but it will not correct the stewardship failure or prevent recurrence.

• Monthly deduplication treats reporting symptoms but leaves the source-process and authority problem unresolved.
• Lowering the threshold weakens a valid business rule instead of addressing the known governance constraint.
• More profiling is unnecessary because the defect, rule, business impact, and delay pattern are already visible.

Question 2

Topic: Quality Governance Roles and Stewardship

A regional insurer discovers that Policy Status has different values in the policy administration system, the claims data mart, and an executive lapse report. The value is a shared data element, and the disagreement is affecting renewal decisions. The source-system team can change capture controls, but business stakeholders have not agreed on the definition or quality rule. What action best fits the accountability need?

Options:

• A. Ask the report owner to standardize the report calculation.

• B. Let each consuming area define its own status rule.

• C. Have the source-system team choose the valid values.

• D. Create a stewardship RACI for Policy Status.

Best answer: D

Explanation: Shared data elements need explicit accountability because quality issues often cross systems, reports, and business processes. A stewardship RACI or similar responsibility assignment clarifies the business data owner accountable for the meaning and fitness-for-purpose rule, the steward coordinating issue resolution, the source-system owner responsible for capture and validation controls, and report owners responsible for correct downstream use. This avoids treating the defect as only a reporting problem or only a system problem. For a recurring inconsistency that affects business decisions, the sustainable response is to assign ownership for the definition, rule approval, implementation, and remediation tracking.

• Report-only fix may hide the symptom in one output but does not settle the shared definition or prevent upstream recurrence.
• Technical value choice gives the system team decision rights that belong with accountable business ownership and stewardship.
• Local status rules increase inconsistency because consumers would continue applying different meanings to the same shared element.

Question 3

Topic: Quality Governance Roles and Stewardship

A customer data stewardship group has documented recurring duplicate customer records across three business units. The group publishes a monthly scorecard and recommends a standard matching rule, but each unit continues to use its own rule and rejects remediation work that affects its local process. The group has no authority to resolve the disagreement. What is the best response?

Options:

• A. Cleanse the duplicates monthly in the warehouse

• B. Increase profiling frequency for duplicate detection

• C. Escalate to governance to assign enforceable decision rights

• D. Let IT choose and implement the matching rule

Best answer: C

Explanation: Data quality stewardship is effective only when it is integrated with governance authority. In this case, the defect is already measured and the preferred rule is known, but the issue persists because business units can reject the shared rule and avoid remediation. The appropriate response is to escalate through data governance so decision rights, accountability, and enforcement are clear. A data owner, council, or governance forum must be able to approve the enterprise rule, resolve conflicts, and require process changes where needed. More measurement or downstream cleanup may help visibility, but it does not solve the authority gap that allows the defect to recur.

• More profiling adds evidence but does not make any unit accept a shared quality rule.
• Warehouse cleansing treats symptoms downstream while source processes continue creating duplicates.
• IT-only selection bypasses business accountability for fitness for purpose and rule ownership.

Question 4

Topic: Quality Governance Roles and Stewardship

A bank’s monthly customer profitability report excludes 12% of customers targeted for a retention campaign. Profiling shows customer identifiers are valid and complete, but the business meaning of “active customer” differs between CRM and billing. The integration mapping converts some suspended billing statuses to inactive, and the BI report uses an undocumented retention-team filter. The data quality council must assign accountability so the defect is fixed and prevented across the lifecycle. Which quality decision is best?

Options:

• A. Make the BI report owner accountable because the campaign impact appears in reporting.

• B. Assign a business data owner and steward to approve the definition and rule, with process owners remediating controls.

• C. Make the integration team solely accountable because the mapping changed customer status.

• D. Make the CRM process owner accountable because CRM is the first customer source.

Best answer: B

Explanation: Quality accountability should follow business meaning and lifecycle responsibility. Here, the defect is not just a report error or a single mapping bug: it spans the definition of “active customer,” source-process interpretation, integration logic, and downstream use. A business data owner, supported by a steward, should be accountable for approving the shared definition, quality rule, threshold, and escalation path. The CRM, billing, integration, and BI owners then remain responsible for implementing and monitoring controls in their parts of the flow. This separates rule ownership from technical implementation while still assigning remediation work to the right operational areas.

• Reporting-only ownership misses the upstream definition and mapping causes, so it would likely create a local workaround.
• Integration-only ownership treats one transformation as the whole defect and leaves the business rule unresolved.
• Source-only ownership ignores billing semantics, integration logic, and the undocumented BI filter that also affect fitness for purpose.

Question 5

Topic: Quality Governance Roles and Stewardship

A customer churn dashboard shows duplicate customer records and inconsistent customer status values. The CRM source team says the BI reporting team owns the issue because executives see it in the dashboard. The BI team says the CRM team owns all customer data quality. Which role clarification is most appropriate for sustained data quality accountability?

Options:

• A. Assign rule ownership to the data owner/steward, with source and reporting teams accountable for their process controls.

• B. Make the BI team accountable because the defects are visible in certified reports.

• C. Make the CRM team accountable for all defects, including report calculations and transformations.

• D. Make the data quality team accountable because it manages profiling, scorecards, and issue logs.

Best answer: A

Explanation: Data quality accountability should follow business ownership and lifecycle responsibility, not only where a defect is discovered. A data owner or steward clarifies the business definition, quality rules, thresholds, and remediation priority for customer data. The CRM/source team is accountable for controls over data captured and maintained in the source process. The BI/reporting team is accountable for transformation logic, metric definitions, presentation, and reporting controls. Data quality specialists may profile data, maintain scorecards, and facilitate issue management, but they do not replace accountable business and process owners. The key distinction is accountability for fitness for purpose versus responsibility for implementing and operating specific controls.

• BI-only ownership confuses defect visibility with accountability; reports may reveal issues that originate earlier in the lifecycle.
• CRM-only ownership ignores reporting responsibilities for transformations, metric logic, and certified presentation.
• Data quality team ownership mistakes facilitation and measurement work for business and process accountability.

Question 6

Topic: Quality Governance Roles and Stewardship

A bank’s monthly regulatory report shows different “active customer” counts from Retail Banking and Compliance. Each domain uses a different definition, and prior remediation tickets closed only by adjusting downstream report logic. The discrepancy has reappeared for three reporting cycles and may affect a regulator-submitted metric. What governance path best fits the situation?

Options:

• A. Ask the reporting team to add another reconciliation check

• B. Open a low-priority defect for the next reporting release

• C. Have Retail Banking publish its definition as the enterprise standard

• D. Escalate to the data governance council for definition ownership and cross-domain remediation

Best answer: D

Explanation: A quality issue with multiple domains, conflicting business definitions, recurring remediation failure, and regulatory exposure needs formal governance escalation. The governance path should bring accountable data owners and stewards together to approve the business definition, assign ownership, agree on quality rules and thresholds, and sponsor root-cause remediation at the source or shared process level. Downstream report fixes may reduce visible variance temporarily, but they do not resolve the underlying semantic conflict or accountability gap. Regulatory impact also raises the need for documented decisions, issue tracking, and evidence that remediation is controlled and sustainable.

• Reporting-only control may detect future differences, but it does not settle ownership or eliminate the recurring cause.
• Single-domain standard is inappropriate because an enterprise definition cannot be imposed by one affected domain when Compliance is also accountable.
• Low-priority handling fails because repeated defects and potential regulatory impact require timely escalation and governance oversight.

Question 7

Topic: Quality Governance Roles and Stewardship

A customer data scorecard shows that billing address completeness is below the approved threshold. The Customer domain steward wants to delay remediation because the defect starts in a Sales intake process, while the Finance steward says invoices are being rejected and wants immediate priority. The stewards cannot agree on ownership, threshold tolerance, or remediation priority. What should happen next?

Options:

• A. Ask IT to cleanse rejected invoices

• B. Escalate to the cross-domain governance council

• C. Let Finance redefine the rule locally

• D. Remove the metric from the scorecard

Best answer: B

Explanation: When a quality issue crosses domains and the responsible stewards cannot resolve ownership, thresholds, or remediation priority, the issue should move through the governance escalation path. DAMA-aligned data quality management depends on defined decision rights: stewards manage quality within their domains, but unresolved cross-domain conflicts require a governance forum with the authority to balance business impact, accountability, and enterprise standards. In this case, Sales creates the defect, Customer data is affected, and Finance suffers the operational impact. A cross-domain governance council can assign accountability, approve or adjust thresholds, and prioritize remediation based on enterprise value rather than one domain’s preference. Local fixes may reduce symptoms, but they do not settle decision rights or prevent recurrence.

• Local rule change fails because Finance cannot unilaterally redefine an enterprise quality rule that affects other domains.
• Technical cleansing treats rejected invoices after the fact but does not resolve ownership or source-process accountability.
• Metric removal hides the issue and weakens governance rather than addressing the threshold breach and business impact.

Question 8

Topic: Quality Governance Roles and Stewardship

A monthly data quality scorecard shows the same customer status-code exceptions for four consecutive cycles. Operations corrects the failed records each month, but the source application team has not changed the entry process. The data steward wants durable prevention, a documented business decision on acceptable codes, and accountable follow-up. What is the best stewardship practice?

Options:

• A. Perform another one-time cleansing of the invalid records

• B. Increase the scorecard frequency to weekly for the same rule

• C. Ask report users to filter out invalid status codes

• D. Open a governed quality issue with root-cause analysis and assigned remediation ownership

Best answer: D

Explanation: Repeated quality exceptions need stewardship-led issue management, not only more measurement or cleanup. A steward should log the recurring defect as a governed quality issue, confirm the business rule for valid status codes, document the decision and threshold, identify the root cause in the source process, assign remediation ownership, and track closure evidence. This turns exceptions into prevention by changing the process or control that creates the defect. Scorecards remain useful evidence, but they do not by themselves create accountability or prevent recurrence.

• More frequent scorecards may reveal exceptions sooner, but measurement alone does not assign ownership or fix the source process.
• One-time cleansing improves current records, but the same defect will recur if the entry process remains unchanged.
• User filtering hides bad data in reports and shifts responsibility downstream instead of resolving the governed quality issue.

Question 9

Topic: Quality Governance Roles and Stewardship

A customer analytics team reports that duplicate customer records are inflating churn metrics and causing conflicting contact preferences in campaign systems. Profiling shows duplicates are concentrated in records created by two onboarding channels, but the matching rule is still informal and business units disagree on which exceptions should be merged automatically. Remediation capacity is limited this quarter, and customer communications must not violate consent preferences. What is the best stewardship-led quality decision?

Options:

• A. Convene stewards to formalize rules, triage exceptions, coordinate fixes, and communicate status

• B. Publish the duplicate rate on a dashboard and defer remediation

• C. Ask IT to block duplicate creation until all records are manually reviewed

• D. Run a one-time deduplication job using the highest-confidence match score

Best answer: A

Explanation: Data stewardship supports sustained quality management by connecting business meaning, rule ownership, exception handling, remediation, and communication. In this scenario, the issue affects churn reporting and customer consent, so a purely technical cleanup is not enough. Stewards should help define and approve matching and survivorship rules, decide which exceptions require human review, triage the most business-critical defects, coordinate source-process fixes with onboarding owners, and communicate impacts and progress to analytics, campaign, and governance stakeholders. Limited remediation capacity makes prioritization especially important. The consent constraint also means automatic merging must be governed carefully rather than based only on a match score.

• One-time cleanup may reduce duplicates temporarily, but it does not resolve informal rules, exception review, source-process causes, or stakeholder alignment.
• Blocking creation is too disruptive and shifts the issue to IT without agreed business rules or a prioritized remediation plan.
• Dashboard only measures the defect, but measurement without triage and coordinated remediation does not address the business risk.

Question 10

Topic: Quality Governance Roles and Stewardship

A customer analytics team finds that 18% of customer records lack a valid consent status. The CRM administrator can enforce field validation, data entry staff can correct missing values during onboarding, and report consumers can flag suspicious records. Under a DAMA-aligned quality governance model, who should be accountable for deciding the acceptable quality threshold and approving the rule for consent status?

Options:

• A. CRM system administrator

• B. Business data owner for customer consent

• C. Data entry team lead

• D. Analytics report consumers

Best answer: B

Explanation: Quality ownership is different from technical custody, operational data capture, and consumer feedback. The accountable business data owner determines what quality means for the data in its business context, including acceptable thresholds, approved rules, and remediation priority. A system administrator may implement controls, data entry staff may follow procedures and correct values, and report consumers may identify defects or impacts. Those roles contribute to quality management, but they do not own the business decision about fitness for purpose. Accountability should remain with the role that can balance business meaning, risk, policy, and use of the data.

• Technical custody fails because administering the CRM supports enforcement but does not define business acceptability.
• Data entry responsibility fails because correcting values is operational execution, not ownership of the quality standard.
• Consumer feedback fails because report users can report issues but do not approve enterprise quality rules.

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
• Metadata Lineage and Quality Evidence
• Master Reference and Warehouse Quality
• Quality in Data Lifecycle and Operations
• Quality Maturity and Continuous Improvement
• Specialist Cross-Discipline Judgment