CDMP — DAMA Data Management Fundamentals Exam Blueprint

How to Use This Exam Blueprint

Use this checklist as a practical study map for the DAMA International DAMA CDMP Data Management Fundamentals exam, exam code CDMP. It is organized around the data management knowledge areas and readiness skills a candidate should be able to apply, not just define.

For each area, ask:

• Can I explain the concept in plain language?
• Can I recognize the right term in a scenario?
• Can I distinguish similar concepts?
• Can I identify the best next action for a data management problem?
• Can I connect the topic to governance, quality, security, architecture, and business value?

This page does not state official exam weights or scoring rules. Treat each area as part of your final review until you can handle terminology, principles, roles, artifacts, and decision scenarios confidently.

Topic-Area Readiness Table

Core Concepts You Should Be Able to Explain

Data as an Organizational Asset

Check that you can explain:

• Why data has value beyond the system where it is stored.
• How poor data management creates operational, regulatory, financial, and reputational risk.
• Why data management is a business discipline supported by technology, not only an IT function.
• How data ownership, stewardship, and accountability support asset management.
• Why shared definitions and standards reduce rework and inconsistent reporting.

Data Management vs. Data Governance

DAMA Knowledge Area Checklist

Data Governance

You should be ready to answer questions about:

• Governance goals: accountability, consistency, risk management, value realization.
• Decision rights: who can define, change, approve, access, or retire data.
• Data policies, standards, procedures, and controls.
• Data stewardship roles and responsibilities.
• Data governance councils, working groups, and escalation paths.
• Business glossary ownership and approval workflows.
• Issue management for data defects, definition conflicts, access disputes, and policy exceptions.
• Metrics for governance adoption, policy compliance, data quality improvement, and business impact.
• How governance supports privacy, security, quality, metadata, and master data.

Can you do this?

• Given a conflict between two departments using different definitions for the same metric, identify governance as the mechanism for definition approval and standardization.
• Given recurring data defects, distinguish between fixing individual records and establishing accountability for root-cause prevention.
• Given unclear access approval, identify the need for data classification, policy, and accountable decision rights.

Data Architecture

Review:

• Enterprise data architecture purpose and scope.
• Current-state and target-state data architecture.
• Data flows across applications, platforms, business processes, and external parties.
• Data domains and subject areas.
• Canonical models, integration architecture, and shared data services.
• Architectural principles such as reuse, interoperability, standardization, scalability, and security by design.
• Relationship between business architecture, application architecture, technology architecture, and data architecture.
• Tradeoffs between centralized, federated, distributed, and domain-oriented data approaches.

Data Modeling and Design

Be able to distinguish model types:

Review these modeling concepts:

• Entity, attribute, relationship.
• Primary key, foreign key, candidate key, surrogate key, natural key.
• Cardinality and optionality.
• Normalization and denormalization.
• Business rules and constraints.
• Subtypes and supertypes.
• Model validation with stakeholders.
• Data model governance and version control.
• Dimensional modeling: fact tables, dimension tables, conformed dimensions, slowly changing dimensions, grain.

Common trap: assuming a physical database table is the same thing as a business entity. A business entity represents a concept; a table is an implementation structure.

Data Storage and Operations

Review:

• Operational data stores, relational databases, non-relational stores, files, object storage, and analytical platforms at a conceptual level.
• Backup, recovery, archiving, retention, and disposal.
• Availability, reliability, performance, capacity, and monitoring.
• Database administration responsibilities versus broader data management responsibilities.
• Data lifecycle controls from creation through deletion.
• Operational procedures for changes, incidents, access, and data refresh.
• Data replication, synchronization, and environment management.
• Production versus development/test data handling.

Can you do this?

• Explain why retention rules and disposal procedures are data management concerns, not just storage cost concerns.
• Identify when backup and recovery are insufficient without tested restore procedures.
• Distinguish operational availability requirements from analytical reporting requirements.

Data Security

Study security as a data management responsibility:

• Confidentiality, integrity, and availability.
• Data classification and sensitivity labeling.
• Role-based access, least privilege, segregation of duties.
• Authentication versus authorization.
• Encryption, masking, tokenization, anonymization, and pseudonymization at a conceptual level.
• Privacy principles and responsible handling of personal or sensitive data.
• Logging, monitoring, auditability, and access reviews.
• Security policies, standards, procedures, and exceptions.
• Secure data sharing with third parties.
• Data breach response concepts and escalation.

Data Integration and Interoperability

Review:

• ETL and ELT concepts.
• Batch, real-time, near-real-time, streaming, and event-driven integration.
• APIs, messaging, file transfer, replication, and data virtualization at a conceptual level.
• Source-to-target mapping.
• Transformation rules and data validation.
• Error handling, reconciliation, restartability, and monitoring.
• Data lineage and impact analysis.
• Semantic interoperability: consistent meaning across systems.
• Structural interoperability: compatible formats and schemas.
• Integration governance: standards, reuse, security, and change control.

Decision prompt: If a question describes data arriving correctly formatted but with different business meaning, the issue is not only technical integration. Look for semantic consistency, definitions, governance, and metadata.

Documents and Content Management

Review:

• Structured versus semi-structured versus unstructured information.
• Document lifecycle: creation, capture, classification, storage, access, retention, archival, disposal.
• Records management concepts.
• Taxonomy, tagging, search, indexing, and retrieval.
• Version control and document control.
• Legal hold and defensible disposition concepts.
• Content security and access management.
• Relationship between content management, knowledge management, and data governance.

Readiness check: Can you identify when a problem is about managing records, documents, and unstructured content rather than relational data?

Reference and Master Data

Review:

• Reference data: controlled values, codes, domains, status lists, country codes, product categories.
• Master data: core business entities such as customer, product, supplier, location, employee, asset.
• Master data management goals: consistency, identity resolution, trust, reuse.
• Golden record concepts.
• Match, merge, survivorship, deduplication, and hierarchy management.
• Data stewardship for master and reference data.
• Data ownership and governance of shared domains.
• MDM implementation styles at a conceptual level.
• Downstream impact of changing codes, identifiers, or hierarchies.

Data Warehousing and Business Intelligence

Review:

• Purpose of data warehousing and analytical data stores.
• Difference between operational processing and analytical reporting.
• Facts, dimensions, measures, grain, hierarchies.
• Star schema and snowflake schema concepts.
• Data marts and enterprise data warehouses at a conceptual level.
• BI reporting, dashboards, scorecards, metrics, and KPIs.
• Data lineage from source systems to reports.
• Reconciliation between source data and analytical outputs.
• Historical data, snapshots, and slowly changing dimensions.
• Self-service analytics governance.

Common trap: treating a dashboard problem as only a visualization issue. If users disagree about the number, check definitions, lineage, data quality, transformation rules, and governance.

Metadata Management

Review the three broad metadata categories:

Also review:

• Metadata repositories and data catalogs.
• Business glossaries.
• Data lineage and impact analysis.
• Metadata standards and ownership.
• Metadata capture: manual, automated, embedded in processes.
• Active versus passive use of metadata.
• How metadata supports governance, quality, security, integration, analytics, and compliance.

Can you do this?

• Given a reporting error, trace why lineage matters.
• Given a field name with unclear meaning, identify the value of business metadata.
• Given a planned source-system change, use metadata for impact analysis.

Data Quality

Review common dimensions:

Review the data quality lifecycle:

• Define quality requirements based on business use.
• Profile data to discover patterns and defects.
• Define rules, thresholds, and controls.
• Measure and monitor quality.
• Identify root causes.
• Remediate defects.
• Prevent recurrence through process, system, governance, or training changes.
• Report quality metrics to accountable stakeholders.

Scenario cue: If data defects keep recurring after cleanup, the better answer often involves root cause analysis, process controls, ownership, and governance rather than repeated manual correction.

Cross-Knowledge-Area Decision Checks

Use these prompts to practice exam judgment.

Role and Responsibility Checklist

Be able to distinguish the responsibilities of common roles. Exact titles vary by organization, so focus on function.

Artifact Checklist

You should recognize the purpose of these artifacts and when each is useful.

Terminology Pairs Candidates Often Mix Up

“Can You Do This?” Final Skills Checklist

Before exam day, you should be able to:

• Define data management and explain its business purpose.
• Identify the most relevant DAMA knowledge area from a short scenario.
• Explain how governance, stewardship, ownership, and policy work together.
• Distinguish conceptual, logical, physical, and dimensional models.
• Recognize entities, attributes, keys, relationships, and cardinality in simple examples.
• Explain why metadata is essential for lineage, impact analysis, quality, and governance.
• Select appropriate data quality dimensions for common defects.
• Distinguish one-time data cleansing from sustained quality management.
• Identify when master data or reference data management is needed.
• Explain the difference between business definitions and technical schemas.
• Recognize security controls appropriate to sensitive data handling.
• Explain lifecycle controls: creation, use, retention, archival, and disposal.
• Identify integration concerns beyond file movement, including mapping, meaning, validation, and monitoring.
• Connect BI trust issues to definitions, lineage, transformations, and quality.
• Recognize how architecture guides consistent data movement, reuse, and target-state planning.
• Choose governance escalation when there is a cross-functional data conflict.
• Explain how maturity assessment supports roadmap planning and continuous improvement.
• Avoid choosing tool-first answers when the scenario primarily describes accountability, policy, definition, or process gaps.

Common Weak Areas and Traps

Tool-First Thinking

Many data management questions are not asking which tool to buy. If the scenario describes unclear ownership, conflicting definitions, inconsistent processes, or recurring quality problems, the better answer often involves governance, stewardship, standards, root cause analysis, or policy.

Treating Data Quality as Cleanup Only

Data quality includes requirements, profiling, measurement, monitoring, accountability, prevention, remediation, and continuous improvement. Manual cleanup may be necessary, but it rarely solves the underlying management problem by itself.

Confusing Data Governance With Central Control

Governance is not always a single central team making every decision. It may include federated roles, councils, standards, escalation paths, and business accountability. The key is clear decision rights and consistent policy.

Ignoring Metadata

Metadata is often the bridge between concepts. It supports:

• Data discovery.
• Business meaning.
• Technical understanding.
• Lineage and impact analysis.
• Quality rules.
• Security classification.
• Stewardship and ownership.
• Auditability.

If a scenario asks “where did this value come from?” or “what will break if this field changes?”, think metadata and lineage.

Mixing Operational and Analytical Requirements

Operational systems optimize transactions and process execution. Analytical environments optimize reporting, trend analysis, historical context, and decision support. The exam may test whether you can recognize different design goals.

Missing the Lifecycle Angle

Data management is not only about storing data. Review how data is acquired, created, used, shared, retained, archived, and disposed of. Lifecycle thinking often changes the best answer in privacy, records, quality, and cost scenarios.

Overlooking Business Accountability

Data problems often appear technical but require business decisions:

• What does the term mean?
• Which value is authoritative?
• Who may access it?
• How accurate is accurate enough?
• How long should it be retained?
• Which rule wins when sources disagree?

Scenario Practice Prompts

Use these prompts for rapid self-testing.

1. Two systems define “active customer” differently.

   • Which knowledge areas are involved?
   • Who should approve the standard definition?
   • What artifacts should be updated?

2. A dashboard metric changed after an ETL update.

   • How would lineage help?
   • What metadata would you review?
   • What quality checks should exist?

3. A business unit creates its own customer list because the enterprise list is not trusted.

   • Is this a data quality issue, MDM issue, governance issue, or all three?
   • What short-term and long-term actions differ?

4. A project wants to copy production data into a test environment.

   • What classification applies?
   • What masking or minimization controls may be needed?
   • Who approves the use?

5. A source application changes a field format.

   • What mappings, reports, validations, and downstream processes may be affected?
   • What artifact should reveal the impact?

6. A company has many data policies but low compliance.

   • Are roles and decision rights clear?
   • Are controls embedded in processes?
   • Are metrics and escalation paths defined?

7. A report is technically correct but not useful to decision makers.

   • Are the metrics aligned to business questions?
   • Is the data fit for purpose?
   • Are definitions and context available?

Final-Week Review Checklist

Three to Five Days Out

• Revisit every DAMA knowledge area and write a one-sentence purpose for each.
• Create a comparison sheet for commonly confused terms.
• Review governance roles: owner, steward, custodian, council, architect, quality analyst.
• Practice identifying the best knowledge area from scenario cues.
• Review artifact purposes: glossary, catalog, model, lineage, policy, standard, scorecard, retention schedule.
• Rework missed practice questions by identifying why the wrong options were attractive.
• Focus on scenario judgment, not only vocabulary recall.

One to Two Days Out

• Review data modeling levels and key modeling terminology.
• Review data quality dimensions and root-cause thinking.
• Review metadata types and uses.
• Review master data versus reference data.
• Review privacy and security controls conceptually.
• Review lifecycle terms: retention, archival, disposal, backup, recovery.
• Stop deep-diving into obscure tool features unless they clarify a core concept.

Exam-Day Readiness

• Read each question for the problem being solved, not just keywords.
• Look for accountability, definition, policy, quality, and lifecycle clues.
• Eliminate answers that are too narrow, tool-only, or one-time fixes when the scenario calls for management discipline.
• Prefer answers that address root cause, governance, repeatability, and business alignment when appropriate.
• Watch for terms that sound similar but belong to different knowledge areas.

Practical Next Step

Use this checklist to mark weak areas, then practice with mixed CDMP-style questions that force you to choose between governance, architecture, modeling, quality, metadata, security, integration, and lifecycle responses. After each missed question, write down the concept distinction you missed and the scenario clue that should have pointed you to the better answer.