DAMA CDMP Data Quality Specialist Study Plan
A practical study plan for the DAMA CDMP Data Quality Specialist exam, with 7-day, 14-day, 30-day, and 60/90-day preparation paths.
Orientation
This Study Plan is for candidates preparing for the DAMA International DAMA CDMP Data Quality Specialist exam, exam code CDMP Quality. It is designed for working professionals who need a practical schedule, not a generic reading list.
The plan focuses on turning available study time into a repeatable preparation rhythm:
- Diagnose your current understanding before you over-study familiar topics.
- Review data quality concepts using DAMA-style terminology.
- Practice scenario questions, definitions, and application questions.
- Build a missed-question log and revisit it repeatedly.
- Use timed mock exams to test pacing and decision-making.
- Stop adding new material before the exam so your final review is controlled.
This is an independent study planning resource and is not affiliated with DAMA International.
Which plan should you use?
Choose the shortest plan only if you already have relevant experience with data quality, data governance, or DAMA data management terminology. If you are new to DAMA concepts, use the 60/90-day path when possible.
| Time available | Best for | Approximate study time | Main goal |
|---|---|---|---|
| 7 days | Final review, retake preparation, or experienced candidates | 2-4 hours per day | Stabilize weak areas and improve test readiness |
| 14 days | Candidates with strong data experience but limited specialist review time | 1.5-3 hours per day | Cover all major topics once and drill weak areas |
| 30 days | Most working candidates | 60-90 minutes on weekdays, longer on weekends | Balanced review, practice, and timed mock exams |
| 60/90 days | Candidates new to DAMA terminology or formal data quality programs | 4-7 hours per week | Build concept depth, scenario judgment, and retention |
Use this decision rule:
| If this describes you | Use this path |
|---|---|
| You can already explain data quality dimensions, stewardship, issue management, profiling, and scorecards | 7 or 14 days |
| You work in data but have not studied DAMA terminology closely | 30 days |
| You are newer to data management, governance, or formal data quality operating models | 60/90 days |
| Your diagnostic score is uneven across topics | 30 or 60/90 days |
| You are within one week of the exam | Use the 7-day plan and stop chasing new resources |
Core topic map for CDMP Quality preparation
Do not treat data quality as only cleansing, matching, or tooling. For the DAMA CDMP Data Quality Specialist exam, organize study around concepts, operating models, measurement, governance, and practical application.
| Topic area | What to be able to do |
|---|---|
| Data quality foundations | Explain fitness for purpose, business impact, quality expectations, and the difference between symptoms and root causes |
| Data quality dimensions | Distinguish dimensions such as completeness, validity, accuracy, consistency, uniqueness, timeliness, and conformity in scenarios |
| Data profiling and assessment | Interpret profiling results, identify anomalies, evaluate critical data elements, and connect findings to business rules |
| Requirements and rules | Translate business expectations into measurable data quality rules, thresholds, controls, and acceptance criteria |
| Metrics and scorecards | Understand how quality metrics, trend reporting, dashboards, and issue thresholds support management decisions |
| Issue management | Prioritize defects, classify issues, assign ownership, track remediation, and verify fixes |
| Root cause analysis | Separate source-system defects, process failures, integration problems, metadata ambiguity, and user behavior issues |
| Governance and stewardship | Explain roles for data owners, stewards, custodians, governance bodies, and operational teams |
| Metadata, lineage, and definitions | Use business definitions, lineage, reference data, and metadata to improve quality interpretation and accountability |
| Data lifecycle controls | Place quality checks in acquisition, transformation, integration, reporting, analytics, and operational processes |
| Tools and automation | Understand profiling, standardization, matching, cleansing, monitoring, and workflow capabilities without over-focusing on one product |
| Communication and improvement | Connect data quality to risk, value, trust, regulatory needs, operational efficiency, and continuous improvement |
Start with a diagnostic
Before building a detailed schedule, complete a diagnostic review. The purpose is not to predict your final result. It is to decide where your study time should go.
Diagnostic setup
| Step | Action |
|---|---|
| 1 | Take a mixed set of practice questions under light time pressure. |
| 2 | Mark each missed or guessed question by topic. |
| 3 | Classify the miss: knowledge gap, terminology gap, scenario judgment, careless reading, or time pressure. |
| 4 | Build a weak-area list with no more than 5 priority topics. |
| 5 | Schedule those topics first, not last. |
Diagnostic tags to use
Use simple tags so review stays fast:
| Tag | Meaning |
|---|---|
| DQ-DIM | Data quality dimensions |
| DQ-RULE | Rules, thresholds, requirements |
| DQ-PROFILE | Profiling and assessment |
| DQ-METRIC | Metrics, scorecards, monitoring |
| DQ-ISSUE | Issue management and remediation |
| DQ-RCA | Root cause analysis |
| DQ-GOV | Governance, stewardship, accountability |
| DQ-META | Metadata, definitions, lineage |
| DQ-LIFE | Lifecycle controls and architecture touchpoints |
| DQ-TOOLS | Tooling, automation, cleansing, matching |
Daily practice rhythm
Use the same rhythm almost every study day. Consistency matters more than long, irregular sessions.
60-90 minute study block
| Time | Activity | Output |
|---|---|---|
| 5-10 min | Recall from memory | Write 3-5 concepts without notes |
| 20-25 min | Focused content review | One topic, one page of notes |
| 25-30 min | Practice questions | Timed or semi-timed topic drill |
| 15-20 min | Missed-question review | Log causes and corrections |
| 5 min | Closeout | Pick tomorrow’s first topic |
30-minute minimum version
Use this when work is busy.
| Time | Activity |
|---|---|
| 5 min | Review yesterday’s missed-question log |
| 10 min | Study one narrow concept |
| 10 min | Answer practice questions |
| 5 min | Write one rule, definition, or contrast from memory |
2-hour deep study version
Use this on weekends or high-value review days.
| Time | Activity |
|---|---|
| 15 min | Rapid recall and flash review |
| 35 min | Topic review with examples |
| 35 min | Practice questions |
| 20 min | Missed-question log and rework |
| 15 min | Scenario review or hands-on concept check |
Optional hands-on concept review
The exam is concept-focused, but hands-on review can make data quality ideas easier to remember. Use small examples to connect definitions to actual controls.
For example, when reviewing profiling and rules, practice identifying what each query is testing:
-- Completeness check
select count(*) as missing_email_count
from customer
where email is null or trim(email) = '';
-- Uniqueness check
select customer_id, count(*) as record_count
from customer
group by customer_id
having count(*) > 1;
-- Validity or conformity check
select count(*) as invalid_status_count
from customer
where status not in ('ACTIVE', 'INACTIVE', 'SUSPENDED');
After each example, ask:
- Which data quality dimension is being tested?
- What business rule is implied?
- Who owns the decision about the acceptable threshold?
- How would this issue be monitored over time?
- What root causes could create this defect?
Do not turn preparation into a tooling project. Use hands-on checks only to strengthen concepts.
7-day final review plan
Use this plan if the exam is within one week. Your goal is not to learn everything from scratch. Your goal is to identify the highest-risk gaps, reduce careless errors, and enter the exam with a controlled review set.
7-day schedule
| Day | Main focus | Study actions |
|---|---|---|
| Day 1 | Diagnostic and triage | Take a mixed diagnostic. Build a weak-area list. Review data quality dimensions and key terminology. |
| Day 2 | Profiling, rules, and assessment | Drill profiling concepts, business rules, critical data elements, thresholds, and quality requirements. |
| Day 3 | Metrics, scorecards, and monitoring | Review measurement design, trend interpretation, issue thresholds, dashboards, and management reporting. |
| Day 4 | Governance and stewardship | Review roles, accountability, data ownership, stewardship workflows, policy connection, and escalation. |
| Day 5 | Timed mock exam | Take a timed mock or large timed set. Review every missed and guessed question. |
| Day 6 | Weak-area sprint | Re-study only weak topics from the mock. Rework missed questions. Review scenario traps and terminology contrasts. |
| Day 7 | Light final review | Review notes, definitions, issue workflow, dimensions, and readiness checklist. Stop heavy study early. |
7-day rules
- Stop adding new resources after Day 4 unless a gap is severe.
- Do not spend the final two days reading broad chapters passively.
- Rework missed questions more than once.
- Prioritize DAMA-style terminology over workplace-specific slang.
- Keep the final day light and confidence-building.
14-day focused plan
Use this plan if you have two weeks and already understand general data management concepts. This path gives you one full pass through the major topics, followed by timed practice and targeted repair.
14-day schedule
| Day | Focus | Practice task |
|---|---|---|
| 1 | Diagnostic and topic map | Mixed diagnostic; create weak-area log |
| 2 | Data quality foundations | Drill definitions, fitness for purpose, quality impacts |
| 3 | Data quality dimensions | Scenario questions distinguishing dimensions |
| 4 | Profiling and assessment | Practice interpreting profiling findings |
| 5 | Requirements and business rules | Convert scenarios into measurable rules and thresholds |
| 6 | Metrics and scorecards | Drill monitoring, reporting, trends, and quality KPIs |
| 7 | Issue management | Review defect lifecycle, prioritization, remediation, verification |
| 8 | Timed mixed set | Timed practice; review misses deeply |
| 9 | Root cause analysis | Classify source, process, integration, metadata, and governance causes |
| 10 | Governance and stewardship | Roles, responsibilities, ownership, escalation |
| 11 | Metadata, lineage, and reference data | Definitions, lineage, standardization, reference/master data quality |
| 12 | Full or near-full timed mock | Simulate exam pacing; capture weak topics |
| 13 | Weak-area repair | Rework missed questions; review top 5 weak areas |
| 14 | Final review | Light recall, terminology, exam-day pacing, rest |
14-day emphasis
| If you are weak in | Spend extra time on |
|---|---|
| Definitions | Data quality dimensions, DAMA terminology, roles |
| Scenarios | Identifying the best governance or remediation response |
| Metrics | Linking rules, thresholds, scorecards, and monitoring |
| Issue workflows | Prioritization, ownership, root cause, verification |
| Tooling questions | Tool capability categories, not vendor-specific features |
Stop adding new material after Day 11. Days 12-14 should be mock review, weak-area repair, and final recall.
30-day balanced plan
Use this plan if you want a realistic working-professional schedule. It assumes weekday study blocks of 60-90 minutes and longer weekend review sessions.
Weekly structure
| Week | Goal | Main outputs |
|---|---|---|
| Week 1 | Build the foundation | Diagnostic, topic map, terminology notes |
| Week 2 | Learn the operating model | Rules, metrics, issue management, stewardship |
| Week 3 | Apply concepts in scenarios | Root cause, lifecycle controls, metadata, tools |
| Week 4 | Practice under exam conditions | Timed mocks, weak-area sprints, final review |
30-day schedule
| Day | Focus | Study actions |
|---|---|---|
| 1 | Diagnostic | Mixed practice set; tag misses |
| 2 | Study plan setup | Build topic tracker and missed-question log |
| 3 | Foundations | Data quality purpose, value, risk, and business alignment |
| 4 | Dimensions I | Completeness, validity, accuracy, consistency |
| 5 | Dimensions II | Uniqueness, timeliness, conformity, integrity |
| 6 | Practice day | Dimension scenarios and terminology drills |
| 7 | Weekly review | Rework misses; summarize Week 1 concepts |
| 8 | Profiling | Profiling techniques, anomaly detection, assessment outputs |
| 9 | Rules and requirements | Business rules, thresholds, acceptance criteria |
| 10 | Critical data elements | Prioritization, impact, risk, and monitoring scope |
| 11 | Metrics | Quality measures, trends, scorecards, dashboards |
| 12 | Issue management | Defect lifecycle, ownership, escalation, verification |
| 13 | Timed topic set | Mixed practice on profiling, rules, metrics, issues |
| 14 | Weekly review | Update weak-area list; rework all Week 2 misses |
| 15 | Midpoint mock | Timed mock or large timed set |
| 16 | Mock review | Analyze errors; assign repair topics |
| 17 | Root cause analysis | Source, process, integration, metadata, governance causes |
| 18 | Governance | Owners, stewards, custodians, governance forums |
| 19 | Metadata and lineage | Definitions, lineage, traceability, context |
| 20 | Reference and master data quality | Standardization, consistency, duplication, ownership |
| 21 | Weekly review | Scenario drills across governance and metadata |
| 22 | Lifecycle controls | Quality checks in ingestion, transformation, reporting, analytics |
| 23 | Tools and automation | Profiling, cleansing, matching, monitoring, workflow |
| 24 | Communication and value | Business case, risk, cost of poor quality, continuous improvement |
| 25 | Timed mock | Full or near-full exam simulation |
| 26 | Mock review | Deep review of missed and guessed questions |
| 27 | Weak-area sprint I | Top 3 weak topics only |
| 28 | Weak-area sprint II | Rework misses; timed mixed set |
| 29 | Final review | Dimensions, roles, workflows, metrics, terminology |
| 30 | Light review | Exam logistics, pacing, confidence check |
30-day stop point
Stop adding new study sources after Day 24. From Day 25 onward, use:
- Timed practice
- Missed-question review
- Short concept summaries
- Weak-area repair
- Light final recall
60/90-day full preparation path
Use this path if you are starting early, preparing alongside work, or building a stronger DAMA-style data quality foundation.
60-day version
| Phase | Days | Focus | Output |
|---|---|---|---|
| Phase 1 | 1-10 | Diagnostic and foundations | Baseline score, topic tracker, terminology notes |
| Phase 2 | 11-25 | Data quality assessment | Dimensions, profiling, rules, critical data elements |
| Phase 3 | 26-40 | Operating model | Metrics, scorecards, issue management, stewardship |
| Phase 4 | 41-50 | Application | Root cause, lifecycle controls, metadata, tools, scenarios |
| Phase 5 | 51-60 | Exam readiness | Timed mocks, weak-area sprints, final review |
90-day version
| Phase | Weeks | Focus | Output |
|---|---|---|---|
| Phase 1 | 1-2 | Orientation and diagnostic | Topic map, baseline, study routine |
| Phase 2 | 3-4 | Foundations and dimensions | Definition mastery and scenario contrasts |
| Phase 3 | 5-6 | Profiling, rules, and requirements | Rule design and assessment interpretation |
| Phase 4 | 7-8 | Metrics, monitoring, and issue management | Scorecard and defect workflow fluency |
| Phase 5 | 9-10 | Governance, stewardship, metadata, lineage | Accountability and context-based decision-making |
| Phase 6 | 11 | Tools, lifecycle controls, and improvement | Practical application review |
| Phase 7 | 12-13 | Timed mocks and final repair | Exam pacing and weak-area closure |
Weekly routine for 60/90 days
| Day type | Activity |
|---|---|
| Study day 1 | Learn or review one topic |
| Study day 2 | Practice questions on that topic |
| Study day 3 | Scenario review and missed-question repair |
| Weekend block | Mixed timed set, notes consolidation, weak-area review |
A sustainable week might look like this:
| Day | Study task |
|---|---|
| Monday | Read/review one focused topic |
| Tuesday | Topic drill and missed-question log |
| Wednesday | Rest or 30-minute flash review |
| Thursday | Scenario practice |
| Friday | Rework older missed questions |
| Saturday | Longer mixed practice block |
| Sunday | Weekly summary and next-week planning |
Missed-question review method
Your missed-question log is more important than your raw practice volume. A candidate who reviews 200 questions carefully often improves more than a candidate who rushes through 800 questions.
Use this log format
| Field | What to record |
|---|---|
| Date | When you missed it |
| Topic tag | Example: DQ-DIM, DQ-GOV, DQ-METRIC |
| Prompt clue | The phrase or concept that should have guided you |
| Your error type | Knowledge gap, terminology gap, misread, overthinking, time pressure |
| Correct principle | The rule or concept you should apply next time |
| Action | Review note, flashcard, reattempt date, or scenario comparison |
Review timing
| When | What to do |
|---|---|
| Same day | Understand the explanation and write the correct principle |
| Next day | Reanswer without looking at the explanation |
| 3-4 days later | Rework with similar questions |
| Final week | Review only persistent errors and high-yield concepts |
Common error patterns
| Error pattern | Fix |
|---|---|
| Confusing dimensions | Create contrast cards: completeness vs validity, consistency vs accuracy, uniqueness vs integrity |
| Choosing tool-first answers | Ask what the governance, rule, or root cause step should be before selecting a tool action |
| Missing ownership clues | Identify data owner, steward, custodian, and process owner responsibilities |
| Treating symptoms as root causes | Trace the issue to source, process, integration, metadata, or policy weakness |
| Overlooking monitoring | Connect one-time assessment to ongoing metrics, thresholds, and scorecards |
When to use timed mock exams
Timed mocks should test pacing, judgment, and endurance. They should not replace learning.
| Preparation window | Timed mock schedule |
|---|---|
| 7 days | Day 1 diagnostic and Day 5 timed mock |
| 14 days | Day 1 diagnostic, Day 8 timed set, Day 12 mock |
| 30 days | Day 1 diagnostic, Day 15 midpoint mock, Day 25 final mock |
| 60/90 days | Baseline in Week 1, one midpoint mock, two final-phase mocks |
Mock exam review process
After each timed mock:
- Record your score, but do not stop there.
- Mark every missed and guessed question.
- Group misses by topic.
- Identify whether the problem was content, terminology, scenario judgment, or pacing.
- Re-study only the topics that caused errors.
- Reattempt a similar timed set within 48-72 hours.
Do not take multiple mocks back-to-back without review. The review is where improvement happens.
Final-week rules
The final week should feel narrower than the rest of your preparation.
Do this
- Review data quality dimensions until you can distinguish them in scenarios.
- Rehearse issue management from detection to verification.
- Review governance roles and accountability.
- Practice interpreting profiling, metrics, and scorecard scenarios.
- Rework your highest-value missed questions.
- Use timed sets to maintain pacing.
- Sleep and exam logistics should become part of the plan.
Avoid this
- Starting a new large textbook or course.
- Memorizing tool-specific details that are not tied to concepts.
- Taking mock after mock without reviewing errors.
- Studying only your favorite topics.
- Changing your strategy in the final 24 hours.
- Doing heavy late-night study immediately before the exam.
Exam-readiness checks
Use these checks before you decide whether to sit as scheduled or adjust your plan.
| Readiness area | You are ready when… |
|---|---|
| Terminology | You can explain core data quality terms without notes |
| Dimensions | You can classify scenario defects by likely dimension |
| Rules and metrics | You can connect requirements to measurable rules and scorecards |
| Governance | You know who should own, steward, escalate, and remediate issues |
| Root cause | You can distinguish symptoms from underlying causes |
| Practice performance | Your timed practice is stable, not dependent on familiar questions |
| Review discipline | Your missed-question log is shrinking in repeated weak areas |
| Pacing | You can finish timed sets without rushing the final questions |
If you are borderline, do not simply add more reading. Use a targeted repair cycle:
| Step | Action |
|---|---|
| 1 | Pick the top 2 weak topics from your log |
| 2 | Review concise notes for each |
| 3 | Complete a timed topic drill |
| 4 | Rework misses immediately |
| 5 | Repeat with a mixed set the next day |
High-yield final review checklist
Before the exam, make sure you can answer these prompts clearly.
Data quality concepts
- What does “fitness for purpose” mean in a business context?
- How do common data quality dimensions differ?
- Why can one defect affect multiple dimensions?
- How do business rules become measurable quality checks?
- Why is threshold setting a business decision, not only a technical one?
Assessment and monitoring
- What is the purpose of profiling?
- How do profiling results support prioritization?
- What makes a data quality metric useful?
- How are scorecards used for management and improvement?
- How do monitoring controls differ from one-time cleanup?
Governance and operating model
- Who is accountable for data quality decisions?
- What is the role of a data steward?
- When should issues be escalated?
- How do metadata and lineage support quality improvement?
- How should root cause analysis guide remediation?
Scenario judgment
- Is the issue a data defect, process defect, governance gap, or metadata ambiguity?
- What is the best next step: define, measure, assign, remediate, monitor, or escalate?
- Is the answer asking for prevention, detection, correction, or communication?
- Is the scenario asking about a one-time project or ongoing quality management?
Practical next step
Start with a diagnostic mixed practice set, then choose the 7-day, 14-day, 30-day, or 60/90-day schedule based on your results. Keep one missed-question log, review it daily, and use timed mocks only when you are ready to learn from the results.