Free DAMA CDMP Quality Practice Questions: Monitoring Scorecards and Measurement

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: Monitoring Scorecards and Measurement

A daily quality monitor for the customer analytics dataset flags a sudden failure: referential integrity to the approved customer master dropped from 99.8% to 82.1% after the overnight load. Lineage shows the CRM export file was not delivered, so the integration process used an outdated cross-reference table. The rule, threshold, and business definition have not changed. Who should receive the alert first?

Options:

• A. The customer data owner

• B. The customer data steward

• C. The data governance forum

• D. The data integration operational team

Best answer: D

Explanation: Alert routing should match the nature of the quality failure and the action needed. Here, the defect is not a disputed rule, an unclear definition, or a policy decision. The monitor and lineage evidence point to a failed CRM file delivery that caused the integration process to use stale reference data. That is an operational incident affecting data quality, so the first notification should go to the team able to restore the feed, rerun the process, and confirm recovery. Stewardship may review the impact afterward, but the first response should remove the operational cause.

• Steward review is useful for rule interpretation or recurring quality defects, but the visible cause is a failed delivery process.
• Owner escalation fits business risk acceptance or funding decisions, not the first response to a fixable load incident.
• Governance forum fits unresolved cross-domain policy or standard conflicts, which are not present here.

Question 2

Topic: Monitoring Scorecards and Measurement

A data quality scorecard for customer master data is reviewed at the monthly stewardship meeting. The country_code_validity rule requires an approved ISO country code before records enter matching and survivorship.

Which action best follows from the scorecard trend?

Options:

• A. Change web capture to use governed reference values

• B. Raise the threshold to match the new channel rate

• C. Run a one-time cleanse of March and April records

• D. Continue warehouse mapping because reports are corrected

Best answer: A

Explanation: A scorecard breach with a rising exception trend should drive action against the cause of the defect, not just activity around the symptoms. Here, the failed rule is validity: country values must match an approved ISO reference set before matching and survivorship. The notes identify the source process causing the defect: a new web channel permits free-text country entry. Warehouse mapping may protect reports, but it does not make the customer master fit for purpose or prevent bad values from affecting matching, survivorship, and downstream reuse. The appropriate response is a governed remediation action that changes the source capture control and uses approved reference data.

• Downstream mapping hides the defect in reports but leaves invalid master data entering core processing.
• Threshold rebaselining is not justified because the business rule has not changed; performance has deteriorated.
• One-time cleansing repairs existing exceptions but does not stop the recurring source-process failure.

Question 3

Topic: Monitoring Scorecards and Measurement

A regional insurer monitors customer address quality because returned policy documents can delay regulatory notices. A profiling run shows address completeness is currently above the approved threshold, but weekly exception counts have risen for five consecutive weeks after a new onboarding workflow was introduced. Data stewards have limited capacity, and the business owner wants evidence that the onboarding control is still effective. What is the best quality decision?

Options:

• A. Run a one-time cleansing job on incomplete addresses

• B. Lower the completeness threshold until stewards have capacity

• C. Close the issue because the current threshold is still met

• D. Add trend-based alerts and review control performance with the owner

Best answer: D

Explanation: Continuous monitoring is not limited to detecting a threshold breach. It also shows whether exception trends are worsening, whether a source-process control remains effective, and when governance review is needed before business impact increases. In this scenario, the current completeness level is acceptable, but the rising weekly exception trend after a workflow change is an early warning. Adding trend-based alerts and reviewing the onboarding control with the business owner supports sustained quality management without waiting for returned documents or regulatory delays to worsen. A one-time cleanup may reduce current defects, but it does not explain whether the new workflow is producing more exceptions.

• Threshold-only thinking misses the fact that a worsening trend can require action before the approved limit is breached.
• One-time cleansing treats symptoms but does not test whether the onboarding process control is still working.
• Lowering the threshold weakens the quality standard and hides risk instead of managing it through governance and monitoring.

Question 4

Topic: Monitoring Scorecards and Measurement

A customer master data team has resolved a recurring duplicate-record defect caused by nightly CRM imports. Profiling shows that duplicates usually appear first in two high-volume regions and then affect downstream billing within 24 hours. Stewards can review about 40 exceptions per day, and the match rule has been approved by data governance but still produces some false positives. Which monitoring approach is the best quality decision?

Options:

• A. Run daily targeted monitoring with thresholded exception queues

• B. Stop monitoring until the match rule has no false positives

• C. Review duplicate rates only in a monthly scorecard

• D. Alert stewards on every possible duplicate from all regions

Best answer: A

Explanation: Continuous monitoring should be risk-based and actionable. The defect is recurring, has a short downstream impact window, and first appears in known high-volume regions. A daily targeted control on the CRM import, using the approved match rule with thresholds or prioritization, gives early detection without flooding stewards. The exception queue should focus on records most likely to affect billing and stay within review capacity. A scorecard can still summarize trends, but it is not enough by itself when action is needed within 24 hours.

The key is to monitor where the defect emerges, at a frequency aligned to business impact, and with alerting tuned to stewardship capacity.

• Every possible duplicate creates alert fatigue because the rule still has false positives and stewards have limited daily review capacity.
• Monthly scorecarding is useful for trend reporting but too slow for a defect that can affect billing within 24 hours.
• Waiting for perfection delays control of a known recurring issue; approved rules can be monitored with thresholds and refinement.

Question 5

Topic: Monitoring Scorecards and Measurement

A continuous monitoring rule for the customer hub sends an alert when invalid reference codes exceed 0.5%. At 02:00, invalid country_code values jump to 14%. Profiling shows all exceptions come from a new interface deployed overnight, and lineage shows the integration mapping did not include the latest approved reference codes. Campaign users are blocked until the load is corrected. Who should receive the primary immediate alert?

Options:

• A. Customer data steward

• B. Operational data integration team

• C. Data governance council

• D. Customer data owner

Best answer: B

Explanation: Alert routing should match the action needed. Here, monitoring has detected a threshold breach, but the decisive evidence is operational: the issue began after an overnight interface deployment, lineage points to an integration mapping gap, and users are blocked until the load is corrected. That makes the immediate alert operational, so the team responsible for the integration and load process can correct the mapping, rerun or recover the load, and reduce business disruption. The steward may need visibility because the rule and reference codes are part of quality management, but the first response is not rule interpretation or policy escalation. Escalation to ownership or governance is more appropriate when business decisions, funding, recurring noncompliance, or cross-domain policy conflicts must be resolved.

• Steward notification is useful for rule context, but the visible evidence already points to an operational mapping failure.
• Owner escalation fits material business decisions or resource tradeoffs, not the first technical recovery step.
• Governance review fits recurring or unresolved policy issues, not an immediate interface-load incident with a clear operational cause.

Question 6

Topic: Monitoring Scorecards and Measurement

A data quality team remediated duplicate customer records that were causing multiple invoices and shipment delays. The monthly scorecard already tracks open defects, defects closed, and average remediation time. Business sponsors now want a KPI that shows whether the remediation improved business performance. Which metric best fits that need?

Options:

• A. Average days to close duplicate defects

• B. Reduction in duplicate-invoice customer complaints

• C. Number of duplicate-record defects closed

• D. Percentage of customer records profiled

Best answer: B

Explanation: Defect activity metrics show how much work the data quality process is doing, such as profiling records, closing issues, or reducing remediation cycle time. Business outcome KPIs show whether better data improved the business process that depends on it. In this case, duplicate customer records created multiple invoices and shipment delays, so a sponsor-facing outcome measure should track the downstream impact, such as fewer duplicate-invoice complaints, fewer delayed shipments, or lower rework cost. Activity measures are still useful for managing the quality program, but they do not prove that business performance improved.

• Closed defects measures remediation throughput, not whether customers or operations saw a better result.
• Closure time measures process efficiency inside issue management, not the business impact of improved customer data.
• Profiled records measures assessment coverage, not the outcome after duplicates are corrected.

Question 7

Topic: Monitoring Scorecards and Measurement

A data quality team is designing a monthly scorecard for customer records used in targeted marketing. Stakeholders need to know whether records are usable for campaigns, especially when consent is missing, country-specific postal codes are invalid, duplicate customer keys exist, or updates arrive after the campaign cutoff. Which KPI set best fits this need?

Options:

• A. Count of records manually corrected each month

• B. Rule pass rates by dimension plus campaign-ready rate

• C. Database uptime and average query response time

• D. Number of profiling jobs run and issues logged

Best answer: B

Explanation: A data quality scorecard should measure whether data is fit for its intended business use, not just whether quality activities occurred. For this case, the scorecard should include metrics such as consent completeness, postal-code validity against country rules, uniqueness of customer identifiers, and timeliness against the campaign cutoff. A combined campaign-ready rate is also useful because it shows the proportion of records that pass all critical rules needed for the marketing process. That connects technical quality dimensions to business fitness for purpose. Activity counts and operational system metrics may be useful elsewhere, but they do not show whether customer records can support the campaign outcome.

• Activity counts show work performed, but they do not measure completeness, validity, uniqueness, timeliness, or fitness for use.
• System performance may affect availability, but uptime and query speed do not assess whether the customer data values are trustworthy.
• Manual corrections show remediation volume, but a correction count can rise or fall without proving that data quality has improved.

Question 8

Topic: Monitoring Scorecards and Measurement

A customer onboarding feed supplies a sanctions screening system every 15 minutes. The quality rule states that legal_entity_id must match an active master data record before screening. Invalid IDs could allow high-risk customers to bypass review, and operations must respond within 10 minutes at the integration point where records first arrive. Which monitoring approach best fits the situation?

Options:

• A. Daily profiling with a weekly data quality scorecard

• B. Monthly stewardship review of master data duplicate rates

• C. Real-time rule validation with alerting and an exception queue

• D. Post-screening BI reconciliation after the reporting load

Best answer: C

Explanation: Continuous monitoring should match the rule’s business impact, lifecycle point, and required response time. Here, the defect must be detected when onboarding records enter the integration layer, before sanctions screening occurs. Because the risk is high and the response window is 10 minutes, batch profiling or periodic scorecarding is too slow as the primary control. A real-time validation check can test the legal_entity_id against active master data, route failed records to an exception queue, and alert operations quickly enough to prevent or contain the business impact. Scorecards can still summarize performance over time, but they do not replace immediate operational monitoring for a critical rule.

• Weekly scorecarding is useful for trend reporting, but it does not meet a 10-minute response requirement.
• Duplicate-rate review addresses a master data quality theme, but it does not monitor the stated identifier-validity rule at ingestion.
• Post-screening reconciliation detects problems after the risky process has already occurred, which is too late for this control need.

Question 9

Topic: Monitoring Scorecards and Measurement

A data steward has implemented a remediation plan for recurring invalid product category codes in a sales data mart. Business users want assurance that the defect will be detected sooner if it returns, that trends will be visible over time, and that the upstream validation control is still working. Which approach best fits this need?

Options:

• A. Manual correction of invalid category codes in reports

• B. Continuous rule monitoring with alerts and trend scorecards

• C. Annual review of the product category glossary

• D. One-time profiling after the next monthly load

Best answer: B

Explanation: Continuous monitoring is used after rules and controls are defined to keep data quality under active management. In this case, the organization needs early warning when invalid codes reappear, trend information across loads, and evidence that the upstream validation control continues to prevent defects. A monitored quality rule with thresholds, alerts, and a scorecard supports all three needs: it detects exceptions quickly, shows whether defect rates are improving or deteriorating, and helps stewards and owners assess control effectiveness. One-time profiling can help discover or baseline defects, but it does not provide sustained detection or trend management. The key is moving from cleanup to ongoing measurement and governance action.

• One-time profiling can establish a baseline, but it does not continuously detect recurrence or show sustained control performance.
• Manual report correction treats downstream symptoms and gives weak evidence about the upstream validation control.
• Annual glossary review supports shared meaning, but it is too infrequent and indirect for early detection and trend analysis.

Question 10

Topic: Monitoring Scorecards and Measurement

A data quality team monitors customer master data used for billing and regulatory reporting. Business stewards have approved rules for completeness, uniqueness, and validity, with thresholds and accountable owners. The governance council wants a recurring view that shows rule results, trends against thresholds, and ownership status so they can decide when to escalate persistent quality failures. Which artifact best fits this need?

Options:

• A. Quality scorecard

• B. Executive dashboard

• C. Issue log

• D. Profiling report

Best answer: A

Explanation: A data quality scorecard is used when quality rules and thresholds are mature enough to be measured repeatedly and compared over time. In this situation, the stewards have approved rules for specific dimensions, and governance needs trend, threshold, owner, and escalation information. That is more than discovery evidence and more structured than a list of defects. A scorecard supports ongoing monitoring and governance decisions by showing whether data remains fit for purpose against agreed measures. An executive dashboard may summarize business KPIs, but it usually does not provide the rule-level stewardship and threshold detail needed for quality management.

• Profiling report is mainly for discovery and assessment of data patterns, not recurring governance monitoring against approved thresholds.
• Issue log records specific defects or incidents, but it does not provide a structured trend view across agreed quality measures.
• Executive dashboard may show high-level status, but it is too summarized for rule-level ownership and escalation tracking.

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