CDMP — DAMA Data Management Fundamentals Study Plan
A practical study schedule for the DAMA CDMP Data Management Fundamentals exam, with 7-day, 14-day, 30-day, and 60/90-day prep paths.
Who this study plan is for
This Study Plan is for candidates preparing for the DAMA International DAMA CDMP Data Management Fundamentals exam, exam code CDMP.
Use it if you need to turn available study time into a realistic schedule. The plan is built around the way Data Management Fundamentals candidates usually need to prepare: broad concept coverage, disciplined terminology review, scenario-based judgment, and repeated practice with missed-question analysis.
The exam rewards more than memorization. You should be able to recognize how data governance, architecture, modeling, quality, metadata, security, master data, warehousing, integration, and operations fit together in a working data management program.
Which plan should you use?
| Time available | Best plan | Use this if… | Main risk | Main priority |
|---|---|---|---|---|
| 7 days | Final review plan | You have already studied most topics and need exam readiness | Too much new material too late | Mock exams, weak areas, terminology |
| 14 days | Focused plan | You know data work but have gaps in DAMA terminology | Shallow coverage across too many areas | Daily domain review plus practice |
| 30 days | Balanced plan | You can study most days and want a steady path | Not testing early enough | Diagnostic first, then topic cycles |
| 60/90 days | Full preparation path | You are new to formal data management or want a stronger foundation | Forgetting early material | Spaced review, notes, repeated mocks |
If you are unsure, take a short diagnostic set before choosing. Your schedule should be based on evidence, not confidence.
| Diagnostic result | Recommended action |
|---|---|
| Strong overall score, few topic clusters missed | Use the 7-day or 14-day plan |
| Moderate score, repeated misses in 3-5 topics | Use the 30-day plan |
| Low score, terminology feels unfamiliar | Use the 60/90-day path |
| Good data experience but poor exam performance | Prioritize DAMA vocabulary, definitions, and role/process distinctions |
Core study areas to rotate through
Do not study CDMP as isolated trivia. Build a connected map of the data management function.
| Study area | What to know how to explain | Practice focus |
|---|---|---|
| Data management foundations | Why data is managed as an asset; data lifecycle; goals of data management | Identify purpose, value, and scope |
| Data governance | Decision rights, policies, stewardship, accountability, standards | Governance vs. management vs. operations |
| Data architecture | Enterprise data structures, principles, alignment with business architecture | Architecture choices and tradeoffs |
| Data modeling and design | Conceptual, logical, and physical models; entities, relationships, normalization basics | Model level recognition and design intent |
| Data storage and operations | Database operations, data availability, lifecycle support, operational controls | Operational responsibilities and risks |
| Data security | Access, privacy, confidentiality, controls, risk reduction | Security responsibility in data programs |
| Data integration and interoperability | Movement, transformation, interfaces, exchange, integration patterns | Best fit for integration scenarios |
| Document and content management | Managing unstructured/semi-structured content, retention, classification | Content governance and lifecycle |
| Reference and master data | Authoritative values, shared entities, consistency across systems | MDM vs. reference data distinctions |
| Data warehousing and business intelligence | Analytics platforms, reporting, dimensional thinking, decision support | Operational vs. analytical use cases |
| Metadata management | Business, technical, and operational metadata; lineage; catalogs | Metadata use in governance and quality |
| Data quality | Dimensions, profiling, rules, issue management, monitoring | Root cause and remediation choices |
| Big data and data science | Analytics lifecycle, large-scale data characteristics, model/data concerns | Fit-for-purpose data and governance |
| Ethics and professional practice | Responsible data handling, trust, accountability, appropriate use | Ethical judgment and risk recognition |
Daily practice rhythm
Use the same structure most study days. This keeps preparation measurable and prevents passive reading.
| Block | Time | Action | Output |
|---|---|---|---|
| Recall warm-up | 10 minutes | Write definitions or explain yesterday’s topics without notes | 5-10 short recall prompts |
| Topic study | 35-60 minutes | Review one focused knowledge area | Condensed notes, not copied text |
| Practice set | 25-45 minutes | Answer questions on the same topic | Score and confidence rating |
| Missed-question review | 25-40 minutes | Analyze every miss and guessed correct answer | Error log entries |
| Integration review | 10-15 minutes | Connect the topic to governance, quality, metadata, or architecture | 3 cross-topic links |
| End-of-day decision | 5 minutes | Choose tomorrow’s weakest target | Next study block selected |
For shorter days, keep the practice set and missed-question review. Reading without feedback is the easiest way to feel prepared while leaving gaps hidden.
Missed-question review method
A missed question is useful only if you classify why it happened. Keep a simple error log.
| Error type | What it means | Fix |
|---|---|---|
| Term confusion | You mixed up two DAMA concepts | Create a contrast card |
| Scope error | You chose an answer from the wrong discipline | Map the question to the right knowledge area |
| Process order error | You misunderstood sequence or dependency | Draw the lifecycle or workflow |
| Role/accountability error | You confused governance, stewardship, operations, or ownership | Write who decides, who executes, who monitors |
| Scenario overthinking | You added assumptions not in the question | Re-answer using only stated facts |
| Memorization gap | You did not know the concept | Add to daily recall list |
| Guess correct | You got it right without certainty | Review as if it were wrong |
Use this format:
| Field | Example entry |
|---|---|
| Topic | Metadata management |
| Question issue | Confused metadata repository purpose with data warehouse purpose |
| Correct principle | Metadata describes data assets, context, lineage, and usage |
| Why I missed it | Focused on reporting instead of asset understanding |
| Review action | Compare metadata, data catalog, warehouse, and BI reporting |
Review the error log every 2-3 days. In the final week, it becomes more important than reading new material.
7-day final review plan
Use this plan only if you have already covered most exam topics. The goal is readiness, not broad first-time learning.
| Day | Main focus | Practice work | Review output |
|---|---|---|---|
| 1 | Diagnostic timed set | Take a timed mixed practice set | Rank weakest 5 topics |
| 2 | Governance, stewardship, ethics | Topic drills plus terminology recall | Governance decision-rights notes |
| 3 | Data modeling, architecture, storage | Scenario questions and contrast review | Model-level comparison sheet |
| 4 | Metadata, data quality, reference/master data | Drill missed concepts | Quality/metadata/MDM distinction table |
| 5 | Integration, warehouse/BI, content, big data/data science | Mixed scenario practice | Analytical vs. operational use cases |
| 6 | Full timed mock or longest available timed set | Simulate exam conditions | Final error log |
| 7 | Light final review | Recall sheets, definitions, weak-area flash review | Stop adding new material |
7-day rules
- Do not start large new resources.
- Do not rewrite notes from scratch.
- Do not spend a full day reading without questions.
- Revisit every guessed-correct answer.
- Stop heavy studying the evening before the exam.
- Use the final day for confidence, recall, logistics, and rest.
14-day focused plan
This plan works well for candidates with professional data experience who need to align that experience to DAMA International terminology and exam-style reasoning.
| Day | Study target | Practice target | End-of-day checkpoint |
|---|---|---|---|
| 1 | Diagnostic and exam map | Mixed baseline set | Identify weak topics |
| 2 | Data management foundations and ethics | Definitions and scenario questions | Explain data as an asset |
| 3 | Data governance | Governance/stewardship/accountability drills | Distinguish decision rights from execution |
| 4 | Data architecture | Architecture principles and enterprise alignment | Connect architecture to strategy |
| 5 | Data modeling and design | Conceptual/logical/physical model questions | Compare model levels clearly |
| 6 | Data storage and operations | Operations, lifecycle, controls | Identify operational responsibilities |
| 7 | Data security | Access, confidentiality, risk, privacy-oriented controls | Link security to governance |
| 8 | Data integration and interoperability | Integration scenarios | Select fit-for-purpose integration approaches |
| 9 | Document/content management and reference data | Classification, retention, controlled values | Separate content, reference, and master data |
| 10 | Master data management | Shared entities, consistency, stewardship | Explain MDM value and challenges |
| 11 | Data warehouse and BI | Analytical use cases and reporting support | Separate operational and analytical data |
| 12 | Metadata and data quality | Lineage, definitions, quality dimensions, issue management | Connect metadata to quality improvement |
| 13 | Timed mock | Full or long mixed timed set | Build final weak-area list |
| 14 | Final review | Error log, definitions, light mixed set | Stop new material |
14-day study split
| Activity | Approximate share |
|---|---|
| Topic review | 40% |
| Practice questions | 35% |
| Missed-question review | 20% |
| Final recall and exam readiness | 5% |
If you miss the same concept twice, do not just reread it. Create a contrast note such as:
- Data governance vs. data management
- Data owner vs. data steward
- Metadata vs. master data
- Reference data vs. master data
- Data quality rule vs. data quality dimension
- Data warehouse vs. operational database
- Conceptual vs. logical vs. physical data model
30-day balanced plan
The 30-day plan gives enough time to cover the full body of knowledge, test early, and revisit weak areas before the final week.
Weeks 1-4 overview
| Week | Goal | Main activities | Milestone |
|---|---|---|---|
| 1 | Build the map | Diagnostic, foundations, governance, architecture | You can explain the data management function |
| 2 | Cover core disciplines | Modeling, storage, security, integration | You can distinguish responsibilities and artifacts |
| 3 | Cover information value topics | Content, reference/master data, warehouse/BI, metadata, quality | You can connect quality, metadata, and governance |
| 4 | Convert knowledge into exam readiness | Timed mocks, weak-area sprints, final review | You can answer mixed questions under time pressure |
30-day daily schedule
| Day | Focus | Practice |
|---|---|---|
| 1 | Diagnostic timed set and topic inventory | Mixed baseline questions |
| 2 | Data management foundations | Definitions and lifecycle questions |
| 3 | Ethics and professional responsibility | Scenario judgment questions |
| 4 | Data governance | Governance vs. stewardship drills |
| 5 | Governance review plus weak areas | Mixed governance/foundation set |
| 6 | Data architecture | Architecture scenario questions |
| 7 | Weekly review | Timed mixed set and error log cleanup |
| 8 | Data modeling concepts | Model-level recognition |
| 9 | Data modeling design decisions | Normalization/design intent questions |
| 10 | Data storage and operations | Operational controls and lifecycle |
| 11 | Data security | Access, confidentiality, risk controls |
| 12 | Data integration and interoperability | Movement, transformation, exchange scenarios |
| 13 | Integration/security/storage review | Mixed domain set |
| 14 | Timed checkpoint | Longer timed set |
| 15 | Document and content management | Classification and lifecycle questions |
| 16 | Reference data | Controlled values and standardization |
| 17 | Master data management | Shared entities and consistency scenarios |
| 18 | Data warehousing and BI | Analytical vs. operational use cases |
| 19 | Metadata management | Lineage, definitions, catalog-style scenarios |
| 20 | Data quality | Dimensions, profiling, rules, issue management |
| 21 | Weekly review | Mixed set across days 15-20 |
| 22 | Big data and data science | Fit-for-purpose data and governance questions |
| 23 | Cross-topic review: governance, metadata, quality | Scenario questions |
| 24 | Cross-topic review: architecture, integration, security | Scenario questions |
| 25 | Full timed mock or longest available timed set | Exam-condition practice |
| 26 | Mock review | Rework every miss and guess |
| 27 | Weak-area sprint 1 | Lowest two topics |
| 28 | Weak-area sprint 2 | Next two topics |
| 29 | Final mixed timed set | Pacing and confidence check |
| 30 | Light final review | Error log, definitions, rest |
30-day checkpoints
By the end of each week, you should be able to answer these without notes:
| Checkpoint | You are ready to move on if… |
|---|---|
| Week 1 | You can explain why governance, architecture, and ethics frame the data management program |
| Week 2 | You can separate modeling, storage, integration, and security responsibilities |
| Week 3 | You can connect metadata, quality, master data, and BI to business value |
| Week 4 | You can handle mixed questions without needing the topic label first |
60/90-day full preparation path
Use this path if you want a deeper foundation or if the DAMA vocabulary is new. The difference between 60 and 90 days is pacing, not content. A 90-day plan gives more spacing, more rereview, and less weekly pressure.
Phase structure
| Phase | 60-day timing | 90-day timing | Goal |
|---|---|---|---|
| Phase 1: Orientation and baseline | Days 1-5 | Days 1-7 | Understand the exam scope and identify gaps |
| Phase 2: Foundations and governance | Days 6-15 | Days 8-22 | Build the management framework |
| Phase 3: Core data disciplines | Days 16-32 | Days 23-50 | Study modeling, storage, security, integration |
| Phase 4: Value, quality, and analytics | Days 33-45 | Days 51-70 | Study metadata, quality, MDM, BI, content, data science |
| Phase 5: Exam conversion | Days 46-60 | Days 71-90 | Practice, mocks, weak-area repair, final review |
Phase 1: Orientation and baseline
| Task | Action |
|---|---|
| Build topic inventory | List every major data management discipline you need to study |
| Take a diagnostic | Use a mixed question set before heavy reading |
| Create an error log | Track topic, cause, correct principle, and follow-up |
| Set weekly study blocks | Schedule at least 4 study sessions per week |
| Define success criteria | Decide what mock performance and confidence level you need before scheduling or sitting |
Phase 2: Foundations and governance
| Topic | Study actions |
|---|---|
| Data management foundations | Summarize the purpose of data management, data lifecycle, and data as an asset |
| Ethics | Review responsible data handling and professional judgment scenarios |
| Data governance | Map decision rights, policies, standards, stewardship, ownership, and accountability |
| Data architecture | Connect business strategy, data structures, standards, and enterprise alignment |
Practice approach:
- Start with untimed topic drills.
- After every two topics, complete a mixed set.
- Write contrast notes for similar terms.
- Explain each governance concept in plain business language.
Phase 3: Core data disciplines
| Topic | Study actions |
|---|---|
| Data modeling and design | Compare conceptual, logical, and physical models; review entities, relationships, and design purpose |
| Data storage and operations | Review operational responsibilities, availability, lifecycle, and controls |
| Data security | Connect access, risk, confidentiality, and policy enforcement |
| Data integration and interoperability | Compare integration needs, data movement, transformation, and exchange concerns |
Add light hands-on review if it helps you understand concepts. For example, sketch a simple customer domain model, identify master/reference data, and describe how it would move from an operational system to analytics.
Phase 4: Value, quality, and analytics
| Topic | Study actions |
|---|---|
| Document and content management | Review classification, retention, lifecycle, and governance of unstructured content |
| Reference data | Identify controlled lists and standard code sets used across systems |
| Master data management | Review shared core entities, stewardship, matching, consistency, and business ownership |
| Data warehousing and BI | Compare operational processing with analytical reporting and decision support |
| Metadata management | Review business, technical, and operational metadata; lineage; definitions; catalogs |
| Data quality | Review dimensions, profiling, rules, issue management, root cause, and monitoring |
| Big data and data science | Review fit-for-purpose data, analytics lifecycle, governance, and ethical use |
Practice approach:
- Use scenario questions, not only definition questions.
- Ask: “Which discipline owns this problem?”
- Ask: “Is the issue about meaning, quality, access, movement, structure, or accountability?”
- Revisit governance and metadata throughout this phase because they connect to many topics.
Phase 5: Exam conversion
| Timing | Action |
|---|---|
| Start of phase | Take a timed mixed mock or long timed set |
| After mock | Spend at least as long reviewing as you spent answering |
| Mid-phase | Run weak-area sprints by topic |
| Final 7 days | Use the 7-day final review plan |
| Final 24 hours | Light recall only; no major new content |
Timed mock exam strategy
Timed mocks are not just score checks. They train pacing, question interpretation, and topic switching.
| Prep stage | Mock use | Purpose |
|---|---|---|
| Beginning | Short diagnostic set | Find baseline gaps |
| Middle | Topic and mixed timed sets | Build speed and retrieval |
| 2-3 weeks out | Longer timed mock | Test endurance and cross-topic reasoning |
| Final week | One full or longest available timed mock | Confirm readiness and identify final review targets |
| Last 24 hours | Avoid heavy mocks | Preserve energy and confidence |
After each timed set, review in this order:
- Questions you missed.
- Questions you guessed correctly.
- Questions that took too long.
- Questions where you changed from right to wrong.
- Questions tied to repeated weak topics.
Do not measure readiness only by total score. Also check consistency.
| Readiness signal | What it means |
|---|---|
| Misses are scattered and explainable | You may be near ready |
| Misses cluster in the same 2-3 topics | Do targeted repair before another mock |
| You understand explanations after reading them but cannot recall unaided | Add active recall |
| You perform well untimed but poorly timed | Practice pacing and first-pass decision-making |
| You keep missing governance/metadata/quality distinctions | Rebuild the concept map |
How to answer scenario questions
For Data Management Fundamentals, many questions test which data management discipline, role, artifact, or principle best fits a situation.
Use this decision path:
| If the question is mainly about… | Think first about… |
|---|---|
| Accountability, policy, standards, decision rights | Data governance |
| Structure of enterprise data capabilities | Data architecture |
| Entities, attributes, relationships, design levels | Data modeling and design |
| Database operation, availability, backup, processing support | Data storage and operations |
| Access, confidentiality, risk, protection | Data security |
| Moving or transforming data between systems | Data integration and interoperability |
| Documents, records, unstructured content, retention | Document and content management |
| Standard codes, lists, classifications | Reference data |
| Shared core business entities such as customer, product, supplier | Master data management |
| Reporting, analytics, decision support | Data warehousing and BI |
| Definitions, lineage, context, data catalogs | Metadata management |
| Accuracy, completeness, consistency, profiling, remediation | Data quality |
| Large-scale analytics, models, advanced analytics use | Big data and data science |
| Responsible and appropriate use of data | Ethics |
Weekly review checklist
Use this checklist once per week for longer plans and every other day for shorter plans.
- I completed at least one mixed practice set.
- I reviewed every missed and guessed-correct question.
- I can explain my weakest topic without notes for two minutes.
- I added new contrast notes for confusing terms.
- I connected each topic back to governance, metadata, quality, or architecture.
- I updated my next study block based on evidence.
- I avoided spending all study time on topics I already like.
Final-week rules
The final week should convert knowledge into recall and pacing.
| Rule | Why it matters |
|---|---|
| Stop adding major new resources | New material can create confusion without enough time for consolidation |
| Use your error log daily | Your own misses are the highest-value review source |
| Practice mixed questions | The real challenge is switching topics accurately |
| Review definitions actively | CDMP preparation depends heavily on precise terminology |
| Keep one-page summaries | Long notes are hard to use under final-week pressure |
| Sleep and logistics matter | Fatigue causes avoidable misreads |
What to stop doing in the final 48 hours
- Starting a new book, course, or large question bank.
- Rewriting all notes.
- Taking multiple heavy mocks back to back.
- Debating obscure details that are not tied to repeated misses.
- Studying late enough to damage exam-day alertness.
Exam-readiness checks
Before exam day, you should be able to do the following without notes:
| Skill | Ready if you can… |
|---|---|
| Define core terms | Give short, accurate definitions of major data management disciplines |
| Classify scenarios | Identify the most relevant discipline from a business problem |
| Separate similar concepts | Explain governance vs. management, reference vs. master data, metadata vs. data, and warehouse vs. operational system |
| Apply accountability logic | Recognize who sets policy, who stewards data, and who operates systems |
| Connect disciplines | Explain how governance, metadata, and quality reinforce each other |
| Handle timing | Complete mixed practice within your planned pace |
| Learn from misses | Show that repeated errors have decreased over time |
If you are still missing the same topic cluster repeatedly, do not take another general mock immediately. Spend one study session rebuilding that topic, then drill it, then return to mixed practice.
Practical next step
Choose the path that matches your timeline, take a diagnostic practice set, and build your first error log before doing more reading. For the DAMA International DAMA CDMP Data Management Fundamentals (CDMP) exam, the fastest improvement usually comes from pairing topic review with disciplined missed-question analysis and timed mixed practice.