DAMA CDMP Data Quality Specialist Quick Review

Quick Review purpose

This Quick Review is for candidates preparing for the DAMA International DAMA CDMP Data Quality Specialist, exam code CDMP Quality. Use it to refresh the most testable Data Quality ideas before moving into IT Mastery practice, topic drills, mock exams, and detailed explanations.

The exam is likely to reward candidates who can do more than define terms. You should be able to distinguish similar concepts, choose appropriate quality controls, connect data quality to governance and business value, and reason through realistic data issue scenarios.

High-yield Data Quality mindset

Data quality is not simply “clean data.” It is the degree to which data is fit for its intended business purpose. The same data may be acceptable for one use case and unacceptable for another.

Core decision rule

Ask three questions first:

1. What business process or decision uses the data?
2. What quality requirement makes that use possible?
3. Where in the data lifecycle should the issue be prevented, detected, corrected, or monitored?

If a question asks for the “best” answer, prefer the option that connects data quality to business use, measurable rules, ownership, and sustainable controls rather than one-time cleansing.

Essential vocabulary

Data quality dimensions

Different frameworks use slightly different dimension names. Focus on the concept and the business question each dimension answers.

Dimension distinctions candidates often miss

Validity vs. accuracy

A value can be valid but not accurate.

• Valid: 99999 is a five-digit postal code format.
• Not accurate: it is not the customer’s actual postal code.

Choose validity when the issue is about format, allowed values, or rule conformance. Choose accuracy when the issue is about truthfulness against reality or a trusted source.

Completeness vs. coverage

Completeness usually asks whether required values are present in records that exist. Coverage asks whether the population itself is sufficiently represented.

Example:

• Customer records have email populated: completeness.
• All active customers are included in the data set: coverage.

Timeliness vs. currency

Timeliness is about availability by the required time. Currency is about whether the value is up to date.

Example:

• Yesterday’s file arrived before 8:00 a.m.: timely.
• The address in the file is three years old: not current.

Consistency vs. integrity

Consistency compares values across places or contexts. Integrity often concerns structural relationships and constraints.

Example:

• CRM says customer is active; billing says inactive: consistency issue.
• Order record references a nonexistent customer ID: integrity issue.

Data quality lifecycle

Data quality management is continuous. It is not a single clean-up project.

    flowchart LR
	    A[Define business need] --> B[Identify critical data]
	    B --> C[Define quality requirements]
	    C --> D[Create rules and metrics]
	    D --> E[Profile and assess data]
	    E --> F[Prioritize issues]
	    F --> G[Remediate data and root causes]
	    G --> H[Implement controls]
	    H --> I[Monitor scorecards]
	    I --> C

Lifecycle exam logic

Data quality requirements and rules

A strong data quality rule is specific, testable, tied to business meaning, and owned.

Weak vs. strong rules

Rule types

Data profiling review

Data profiling helps reveal what is actually in the data before defining or refining controls.

Common profiling outputs

Profiling traps

• Profiling finds symptoms; it does not automatically determine root cause.
• A surprising value is not always an error. It may be a legitimate business exception.
• Profiling without business context can produce misleading conclusions.
• Technical profiling should be paired with metadata, definitions, lineage, and process knowledge.
• Do not remediate solely because a value is rare. Confirm business rules first.

Measurement and metrics

Data quality metrics should be understandable, repeatable, actionable, and tied to thresholds.

Common metric structures

Metric quality checklist

A useful data quality metric should have:

• A clear business definition.
• A defined population.
• A clear numerator and denominator.
• An owner.
• A measurement frequency.
• A threshold or target.
• An escalation path.
• A link to business impact.
• A way to distinguish severity, trend, and recurrence.

Data quality scorecards and dashboards

Scorecards communicate quality status. They should support decisions, not just display numbers.

Scorecard trap

A dashboard with many metrics but no ownership, thresholds, or action process is weak data quality management. For exam scenarios, the stronger answer usually links metrics to accountability and continuous improvement.

Issue management

Data quality issues should be logged, triaged, assigned, investigated, resolved, and monitored for recurrence.

Issue management workflow

1. Detect issue through profiling, control failure, user report, audit, or monitoring.
2. Log the issue with evidence, affected data, and business impact.
3. Classify by dimension, severity, domain, and affected process.
4. Assign ownership to appropriate business and technical roles.
5. Analyze root cause rather than only correcting visible records.
6. Remediate data where appropriate.
7. Fix process or control to prevent recurrence.
8. Validate resolution with retesting.
9. Monitor recurrence through ongoing metrics.

Severity decision factors

Root cause analysis

Root cause analysis separates symptoms from causes.

Common root causes

Root cause vs. remediation

Prevention, detection, and correction controls

Data quality controls can be placed at different points in the lifecycle. Prevention is usually preferable when feasible, but detection and correction remain necessary.

Control selection rule

Prefer the control closest to the source of defect creation if it is practical, business-aligned, and does not create unacceptable process friction.

Data cleansing and standardization

Cleansing improves existing data, but it should not be confused with sustainable quality management.

Cleansing techniques

Cleansing traps

• Cleansing without business rules can corrupt data.
• Deduplication can incorrectly merge different real-world entities.
• Enrichment may introduce licensing, trust, lineage, or currency issues.
• Automated correction should be monitored, especially for high-risk data.
• Cleansing projects should feed lessons back into process and control improvement.

Matching, deduplication, and survivorship

Duplicate management is a common scenario area because it requires judgment.

Survivorship examples

Trap

A “golden record” is not automatically true or permanent. It depends on matching logic, source trust, governance decisions, and ongoing updates.

Reference data, master data, and data quality

Data quality issues often arise from poor control of reference or master data.

Examples

Metadata and business glossary

Metadata is essential for data quality because it clarifies meaning, lineage, rules, and responsibility.

Metadata that supports data quality

Exam trap

If a scenario shows inconsistent reporting because teams define the same term differently, the best answer is usually not “clean the database.” It is to resolve definitions, governance, metadata, and lineage.

Governance and accountability

Data quality requires business accountability and cross-functional coordination. IT can implement controls, but business stakeholders define quality requirements and acceptable thresholds.

Typical responsibilities

Accountability trap

Do not assign all data quality responsibility to IT. Technical teams often implement solutions, but data quality requirements, definitions, priorities, and acceptance criteria must be business-led.

Data quality and the data lifecycle

Quality can be affected at every stage.

High-yield idea

The earlier a defect is prevented, the less costly it usually is to fix. However, the best exam answer should still consider feasibility, business impact, and process design.

Data quality in analytics and reporting

Analytics failures often stem from poor definitions, inconsistent transformations, incomplete populations, or stale data.

Candidate mistake

Do not assume every reporting discrepancy is a data warehouse defect. It may originate in source systems, business definitions, integration timing, transformation logic, or report filters.

Data quality and data integration

Data movement can create or reveal quality defects.

Integration quality checks

Trap

A successful file load does not mean the data is fit for purpose. Technical completion and data quality are related but different.

Data quality costs and business value

Data quality initiatives should be justified by business impact, risk reduction, efficiency, and trust.

Cost categories

Business value examples

• Reduced operational rework.
• More reliable reporting.
• Improved customer experience.
• Better regulatory or risk reporting support.
• Reduced duplicate processing.
• Faster integration and migration.
• More trustworthy analytics.
• Improved process automation.

Prioritization

Not all data defects deserve equal effort. Prioritize based on criticality, impact, and feasibility.

Prioritization matrix

Better prioritization considers

• Critical data elements.
• Business process dependency.
• Customer or stakeholder impact.
• Risk and control implications.
• Number of affected records.
• Severity of errors.
• Frequency and recurrence.
• Root cause complexity.
• Remediation cost.
• Availability of preventive controls.

Critical data elements

A critical data element is important enough that poor quality can materially affect business outcomes, risk, reporting, or operations.

How to identify critical data

Look for data used in:

• Key business decisions.
• Executive or regulatory reporting.
• Customer-facing processes.
• Financial calculations.
• Risk models or controls.
• Operational workflows.
• Master data relationships.
• Integration keys.
• Contractual or service obligations.
• High-volume automation.

Trap

A field is not critical merely because it exists in a database. Criticality comes from business use and impact.

Data quality strategy

A mature data quality program is proactive, governed, measured, and continuously improved.

Strategy components

Maturity perspective

Data quality maturity generally progresses from reactive correction to proactive prevention and optimization.

Exam logic

If a scenario asks how to improve maturity, prefer actions that institutionalize ownership, standards, measurement, and root-cause prevention over isolated clean-up.

Common scenario patterns

Scenario: many missing values

Best response depends on why values are missing.

Scenario: duplicate customers

Good answer usually includes:

• Define matching criteria.
• Profile duplicates.
• Establish survivorship rules.
• Assign stewardship review for ambiguous matches.
• Merge or link records carefully.
• Improve capture and matching controls at onboarding.
• Monitor duplicate rate.

Scenario: inconsistent report numbers

Good answer usually includes:

• Compare business definitions.
• Review lineage and transformations.
• Check timing and refresh cycles.
• Reconcile source-to-target counts and totals.
• Identify authoritative source.
• Establish governed KPI definition.

Scenario: invalid reference codes

Good answer usually includes:

• Align code sets and definitions.
• Validate against approved reference data.
• Fix source mappings.
• Add interface controls.
• Establish owner for reference data changes.
• Monitor exceptions.

Scenario: recurring defects after cleansing

Good answer usually includes:

• Perform root cause analysis.
• Fix upstream process or system controls.
• Clarify ownership and rules.
• Add monitoring.
• Avoid another isolated cleansing-only project.

Data quality tools

Tools support data quality work, but they do not replace governance or business rules.

Tooling trap

Selecting a tool before defining business requirements, ownership, and rules is usually not the strongest answer.

Data quality dimensions by example

Use this table for rapid classification practice.

Formulas worth knowing conceptually

You do not need to over-memorize formulas, but you should understand the structure of basic quality rates.

\[ \text{Validity Rate} = \frac{\text{Records Passing Validation Rule}}{\text{Records Tested}} \]\[ \text{Defect Rate} = \frac{\text{Records Failing Quality Rule}}{\text{Records Tested}} \]\[ \text{Completeness Rate} = \frac{\text{Applicable Records With Required Value Present}}{\text{Applicable Records}} \]

Key exam point: define the applicable population carefully. A completeness denominator should exclude records where the field is genuinely not applicable.

Common traps on the CDMP Quality exam

Trap 1: choosing cleansing when governance is needed

If the issue is recurring, cross-system, or definition-based, cleansing alone is insufficient.

Trap 2: confusing technical validity with business correctness

A value can pass a system edit and still be wrong for the business.

Trap 3: ignoring root cause

Sustainable data quality requires preventing recurrence, not only fixing defective records.

Trap 4: treating all data equally

Focus on critical data elements and business impact.

Trap 5: assuming IT owns data quality

IT implements many controls, but business ownership and stewardship are central.

Trap 6: measuring without acting

Metrics are useful only when connected to thresholds, accountability, and remediation.

Trap 7: over-validating at the wrong point

Too many entry controls can slow business processes or create workarounds. Place controls thoughtfully.

Trap 8: using dimensions mechanically

Some issues can involve multiple dimensions. Choose the dimension most directly tested by the scenario.

Trap 9: trusting external data blindly

Third-party or external data requires assessment, contracts or expectations, monitoring, and lineage.

Trap 10: overlooking metadata

Definitions, lineage, and rules are often the missing link in data quality scenarios.

Fast decision rules

Use these when answering scenario questions quickly.

Mini review: from issue to action

What to practice next

After reviewing these concepts, move into IT Mastery practice for the DAMA International DAMA CDMP Data Quality Specialist (CDMP Quality) exam. Start with topic drills on data quality dimensions, profiling, rules, issue management, governance roles, and root-cause scenarios. Then use original practice questions and mock exams with detailed explanations to test whether you can choose the best action in realistic data quality situations.

Continue in IT Mastery

Use this Quick Review as a final concept map, then move into IT Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original IT Mastery practice items; they are not official DAMA questions, copied live-exam content, or exam dumps.