CDMP — DAMA Data Management Fundamentals Quick Review

Last revised: June 25, 2026

Quick Review for DAMA International DAMA CDMP Data Management Fundamentals (CDMP) candidates preparing for topic drills, mock exams, and detailed explanations.

Quick Review Purpose

This Quick Review is for candidates preparing for the real DAMA International DAMA CDMP Data Management Fundamentals (CDMP) exam who want a concise, high-yield review before working through topic drills, mock exams, and detailed explanations.

It is IT Mastery exam-prep support and is not affiliated with DAMA International. Use it to refresh the major data management concepts, sharpen decision rules, and identify weak areas before using an original question bank for deeper practice.

Exam Identity

Item	Detail
Provider	DAMA International
Official exam title	DAMA CDMP Data Management Fundamentals
Official exam code	CDMP
Review focus	Core data management principles, terminology, decision-making, and common exam traps
Best use	Read once, drill weak topics, review explanations, then take mixed mock exams

The Core Mental Model

The CDMP exam rewards candidates who understand data management as a coordinated business capability, not as a set of isolated technical tasks.

A useful mental model:

Layer	What it answers	Examples
Business direction	Why are we managing data?	Strategy, value, risk reduction, compliance support, analytics enablement
Governance	Who decides and who is accountable?	Policies, stewardship, ownership, councils, standards
Architecture and design	How should data capabilities fit together?	Data architecture, models, integration patterns, platforms
Operations	How is data created, stored, moved, protected, and used?	Databases, data pipelines, APIs, warehouses, backups
Controls and improvement	How do we keep data trusted and useful?	Data quality, metadata, lineage, security, monitoring

A common candidate mistake is to treat every issue as a technology problem. In DAMA-style data management, many problems are governance, ownership, definition, quality, or lifecycle problems before they are tool problems.

High-Yield Knowledge Area Map

Use this table as a fast scan before practice questions.

Area	Know the purpose	Watch for these traps
Data governance	Sets decision rights, accountability, policies, standards, and stewardship	Confusing governance with hands-on data administration
Data architecture	Aligns data capabilities, flows, stores, and standards with business needs	Jumping to platform choices before understanding requirements
Data modeling and design	Represents business concepts, relationships, rules, and structures	Mixing conceptual, logical, and physical models
Data storage and operations	Manages databases, storage, availability, backup, recovery, and operational support	Treating backup, recovery, disaster recovery, and business continuity as identical
Data security	Protects confidentiality, integrity, and availability of data	Assuming security is only encryption or only IT’s responsibility
Data integration and interoperability	Moves, shares, transforms, synchronizes, and exposes data across systems	Confusing ETL, ELT, replication, federation, APIs, and streaming
Document and content management	Manages unstructured and semi-structured information through its lifecycle	Ignoring retention, classification, search, and records controls
Reference and master data	Manages shared identifiers, codes, core business entities, and trusted records	Confusing reference data with master data
Data warehousing and BI	Supports reporting, analytics, historical analysis, and decision support	Confusing operational systems with analytical systems
Metadata management	Manages data about data: meaning, structure, lineage, usage, and operations	Treating metadata as only technical column definitions
Data quality	Measures, improves, and monitors fitness for use	Treating cleansing as the same thing as quality management
Big data and data science	Applies scalable data processing and analytic methods to high-volume or complex data	Focusing on buzzwords instead of governance, quality, ethics, and lifecycle controls

Governance: Decision Rights, Accountability, and Control

Data governance is one of the most important CDMP review areas because it connects business accountability to data management execution.

Governance vs. Management

Concept	Primary question	Typical outputs
Data governance	Who has authority and accountability for data decisions?	Policies, standards, decision rights, issue escalation, stewardship model
Data management	How are data capabilities planned, built, operated, and improved?	Models, platforms, processes, controls, data quality rules, metadata repositories
Data stewardship	Who helps define, monitor, and improve data in practice?	Definitions, quality rules, issue resolution, glossary content, usage guidance

Key Governance Roles

Role	Main responsibility	Common trap
Data owner	Accountable for data within a business domain or process	Not necessarily the person who stores or administers the data
Data steward	Helps define, manage, monitor, and improve data	Stewardship is not just clerical cleanup
Data custodian	Operates or administers data systems and storage	Custodians usually do not own business meaning
Data architect	Designs structures, flows, models, and standards	Architecture should support business strategy, not just technical elegance
Data consumer	Uses data for operations, reporting, analytics, or decisions	Consumers also create requirements and quality expectations

Policies, Standards, Procedures, and Guidelines

Item	Meaning	Example
Policy	High-level rule or intent	Sensitive data must be protected according to classification
Standard	Required way to comply	Customer identifiers must follow an approved format
Procedure	Step-by-step method	Process for approving a new data sharing request
Guideline	Recommended practice	Preferred naming pattern for analytics datasets

Exam trap: If the question asks about accountability, authority, escalation, or enterprise-wide rules, think governance. If it asks about execution, operation, implementation, or administration, think management.

Data Strategy and Business Value

Data management should support business outcomes. Candidates often over-focus on definitions and under-focus on purpose.

Business goal	Data management contribution
Better decisions	Trusted, timely, well-defined data and analytics
Operational efficiency	Standardized data, reduced rework, fewer reconciliation issues
Risk reduction	Controls for security, retention, quality, lineage, and access
Regulatory support	Traceable, governed, classified, and auditable data practices
Customer or product insight	Integrated, high-quality data across channels and systems
Innovation	Reusable data assets, scalable platforms, and responsible analytics

A good exam answer often favors the option that improves data as an enterprise asset rather than a narrow local workaround.

Data Architecture

Data architecture describes how data is organized, integrated, stored, shared, and governed across the enterprise.

Architecture Review Points

Concept	What to remember
Enterprise data architecture	Broad view of data domains, flows, systems, standards, and capabilities
Data domain	A major subject area, such as customer, product, supplier, employee, asset, or transaction
Data flow	Movement or sharing of data between processes, applications, stores, and users
Target architecture	Desired future-state design aligned to strategy
Current-state architecture	Existing data environment, including constraints and technical debt
Roadmap	Sequenced path from current state to target state

Common Architecture Traps

Choosing a tool before defining business requirements.
Designing only for one project rather than enterprise reuse.
Ignoring data lineage, ownership, and quality requirements.
Treating architecture diagrams as documentation only, rather than decision-support tools.
Forgetting that architecture must balance business, information, application, and technology concerns.

Data Modeling and Design

Data modeling is a high-yield area because questions often test levels of abstraction, relationships, and business meaning.

Conceptual, Logical, and Physical Models

Model type	Main audience	Focus	Example content
Conceptual	Business stakeholders	Major business concepts and relationships	Customer places Order
Logical	Analysts, data modelers, designers	Attributes, relationships, business rules, normalization	Customer, Order, Order Line, Product with keys and cardinality
Physical	DBAs, engineers, platform teams	Implementation details	Tables, columns, indexes, partitions, datatypes

Decision rule: If the question emphasizes business concepts and shared understanding, choose conceptual. If it emphasizes detailed entities, attributes, and relationships independent of technology, choose logical. If it emphasizes implementation in a specific database or platform, choose physical.

Modeling Concepts to Review

Concept	Meaning	Exam cue
Entity	Thing of business interest	Customer, Product, Invoice
Attribute	Property of an entity	Customer Name, Order Date
Relationship	Association between entities	Customer places Order
Cardinality	Number of instances that can relate	One-to-many, many-to-many
Optionality	Whether relationship participation is required	Customer may have Account
Primary key	Uniquely identifies a record	Customer ID
Foreign key	References another entity’s key	Order contains Customer ID
Domain	Valid set of values	Status code list, date range, allowed category

Normalization and Denormalization

Approach	Purpose	Tradeoff
Normalization	Reduce redundancy and update anomalies	May require more joins
Denormalization	Improve read performance or simplify access	May introduce redundancy and consistency risks

Exam trap: Normalization is not automatically “better” in every context. Operational systems often benefit from normalized design; analytical systems may intentionally use dimensional or denormalized structures for query performance and usability.

Data Storage and Operations

Data storage and operations covers the practical management of databases, storage platforms, operational support, availability, and recovery.

Core Terms

Term	Quick meaning
Database	Organized collection of data managed for access and update
DBMS	Software used to define, store, secure, query, and manage databases
Backup	Copy of data for recovery purposes
Recovery	Restoring data or service after failure
Archive	Long-term storage, often for inactive or historical data
Retention	How long data should be kept based on business and control requirements
Disposal	Controlled deletion or destruction when data is no longer needed
Availability	Ability of systems and data to be accessible when required

Backup, Recovery, DR, and Continuity

Concept	Primary concern
Backup	Having recoverable copies
Recovery	Restoring data or service after an incident
Disaster recovery	Restoring technology capability after major disruption
Business continuity	Maintaining critical business operations during disruption

Common mistake: Selecting “backup” as the complete answer when the question is about broader continuity, resilience, or recovery planning.

Data Security

Data security protects data from unauthorized access, misuse, alteration, disclosure, or loss.

Security Principles

Principle	Meaning	Example
Confidentiality	Only authorized users can access data	Access controls, encryption, masking
Integrity	Data is accurate, complete, and not improperly altered	Validation, checks, audit trails
Availability	Data is accessible when needed	Resilience, monitoring, recovery planning
Least privilege	Users get only the access needed	Role-based access
Defense in depth	Multiple complementary controls	Network, application, database, identity, monitoring

Security Controls to Distinguish

Control	Purpose
Authentication	Verifies identity
Authorization	Determines allowed actions
Encryption	Protects data confidentiality by encoding it
Masking	Hides sensitive values from users or environments
Tokenization	Replaces sensitive values with substitute tokens
Auditing	Records activity for monitoring and investigation
Classification	Labels data based on sensitivity, value, or handling needs

Exam trap: Security is not only a technical function. Governance defines policies and accountability; security teams and custodians implement controls; data owners help determine classification, sensitivity, and acceptable use.

Data Integration and Interoperability

Integration enables data to move between applications, databases, platforms, partners, reports, and analytics environments.

Integration Pattern Review

Pattern	Best fit	Watch out for
ETL	Transform before loading into target	Batch-oriented; transformation happens before load
ELT	Load first, transform in target platform	Often used with scalable analytical platforms
API	Controlled application-to-application access	Requires interface design, security, versioning
Messaging	Event or message exchange between systems	Useful for decoupling systems
Streaming	Near-real-time event processing	Requires attention to latency, ordering, and reliability
Replication	Copies data between environments	Does not automatically resolve meaning or quality issues
Change data capture	Captures changes from source systems	Useful for incremental movement
Data virtualization/federation	Accesses data without physically moving all of it	Performance, governance, and consistency must be considered

Integration Decision Rules

If the issue is meaning, resolve definitions and metadata before building pipelines.
If the issue is timeliness, compare batch, near-real-time, and streaming needs.
If the issue is reuse, consider shared services, APIs, canonical models, and standards.
If the issue is trust, include quality checks, lineage, reconciliation, and monitoring.
If the issue is sensitivity, include classification, access controls, encryption, and masking.

Document and Content Management

Document and content management focuses on unstructured and semi-structured information such as documents, images, web content, emails, records, and knowledge assets.

Concept	Quick meaning
Document management	Controls documents through creation, versioning, storage, retrieval, and disposition
Content management	Broader management of digital content for use, publishing, search, and reuse
Records management	Manages records that provide evidence of business activity
Taxonomy	Controlled structure for classifying content
Search and retrieval	Enables users to find content efficiently
Version control	Tracks changes and current approved versions

Common trap: Treating documents as outside data management. Content still needs ownership, metadata, classification, retention, access control, and quality expectations.

Reference Data and Master Data

Reference data and master data are commonly confused. The distinction is high-yield.

Reference Data vs. Master Data

Type	Meaning	Examples
Reference data	Standard values used to classify or categorize other data	Country codes, currency codes, status codes, product categories
Master data	Core business entities shared across processes and systems	Customer, product, supplier, employee, location, asset

Master Data Management Concepts

Concept	Meaning
Golden record	Best trusted representation of an entity
Matching	Identifying records that refer to the same real-world entity
Merging	Combining duplicate or overlapping records
Survivorship	Rules for selecting the preferred value among conflicting sources
Hierarchy management	Managing parent-child or grouping relationships
Data stewardship	Resolving ambiguous matches, definitions, and quality issues

MDM Implementation Styles

Style	General idea
Registry	Maintains cross-references and identifiers across systems
Consolidation	Combines data for reporting or reference use
Coexistence	Shares updates between master hub and source systems
Centralized	Master data is authored and managed centrally

Exam trap: MDM is not just deduplication software. It requires governance, ownership, quality rules, integration, matching logic, stewardship, and lifecycle management.

Data Warehousing and Business Intelligence

Data warehousing and BI support analysis, reporting, performance management, and decision-making.

Operational vs. Analytical Systems

Feature	Operational systems	Analytical systems
Main purpose	Run business processes	Support reporting and analysis
Data pattern	Current, transaction-focused	Historical, integrated, subject-oriented
Design priority	Fast transactions and integrity	Query performance and usability
Users	Operational staff, applications	Analysts, managers, data consumers
Common design	Normalized relational structures	Dimensional models, warehouses, marts

Dimensional Modeling

Term	Meaning
Fact	Measurable business event or numeric measure
Dimension	Descriptive context for facts
Grain	Level of detail represented by a fact table
Star schema	Fact table connected to dimension tables
Slowly changing dimension	Technique for handling changes in dimension attributes over time

Decision rule: Always identify the grain before evaluating a fact table design. Many dimensional modeling errors come from mixing different levels of detail in the same structure.

BI and Analytics Traps

Confusing dashboards with data governance.
Assuming a report is correct because it was produced by a system.
Ignoring lineage from source to report.
Mixing metrics with different definitions.
Building analytics before agreeing on business terms and calculation rules.

Metadata Management

Metadata is data about data. It makes data understandable, traceable, usable, and governable.

Metadata Types

Type	Describes	Examples
Business metadata	Business meaning and context	Definitions, owners, rules, glossary terms
Technical metadata	Structure and implementation	Tables, columns, datatypes, mappings
Operational metadata	Processing and usage	Job runs, load times, error counts, access logs
Administrative metadata	Management and control	retention, classification, stewardship, ownership

Metadata Capabilities

Capability	Why it matters
Business glossary	Aligns terminology across business and technology teams
Data catalog	Helps users discover, understand, and evaluate data assets
Lineage	Shows where data came from and how it changed
Impact analysis	Helps assess effects of changes
Data dictionary	Describes structures, fields, formats, and constraints
Metadata repository	Stores and manages metadata centrally or federatively

Exam trap: A data dictionary is not the same as a full metadata management program. A dictionary may describe fields; metadata management also includes ownership, lineage, rules, quality, usage, and governance processes.

Data Quality

Data quality means data is fit for its intended use. It is not absolute perfection.

Common Data Quality Dimensions

Dimension	Meaning	Example question
Accuracy	Data correctly represents the real-world value	Is the customer address correct?
Completeness	Required data is present	Is date of birth missing where required?
Consistency	Data agrees across systems or records	Does customer status match in two systems?
Timeliness	Data is current enough for use	Was the balance updated in time for reporting?
Validity	Data conforms to rules or allowed values	Is the status code in the approved list?
Uniqueness	Entity is not duplicated unnecessarily	Are there duplicate customer records?
Integrity	Relationships and constraints are maintained	Does every order reference a valid customer?

Data Quality Activities

Activity	Purpose
Profiling	Examines data to discover patterns, anomalies, and quality issues
Assessment	Evaluates quality against business requirements
Cleansing	Corrects or standardizes data values
Matching/deduplication	Identifies and resolves duplicate entities
Monitoring	Tracks quality over time
Root-cause analysis	Finds why defects occur
Prevention	Improves processes and controls to stop defects at source

High-yield distinction: Cleansing fixes existing data; quality management also prevents future defects through governance, standards, controls, process changes, and monitoring.

Big Data, Data Science, and Analytics Governance

For CDMP review, focus less on buzzwords and more on how data management principles apply at scale.

Concept	What to remember
Big data	Data with volume, velocity, variety, or complexity that challenges traditional approaches
Data lake	Stores raw or varied data for exploration and analytics; still needs governance and metadata
Data lakehouse	Combines lake-style storage with warehouse-like management features
Data science	Uses statistical, computational, and machine learning methods to generate insight or predictions
Machine learning model	Learns patterns from data to make predictions or classifications
Feature	Input variable used by a model
Model governance	Controls model development, validation, deployment, monitoring, and responsible use

Common Analytics Traps

Assuming more data automatically means better results.
Ignoring bias, representativeness, and data provenance.
Using data without understanding definitions and lineage.
Treating models as one-time deliverables rather than lifecycle assets.
Forgetting security, privacy, ethics, and access controls in analytical environments.

Data Lifecycle Review

Data management spans the full lifecycle, not just storage.

Lifecycle stage	Key concerns
Plan	Strategy, requirements, ownership, architecture, standards
Create or acquire	Source quality, definitions, consent or usage expectations, validation
Store and maintain	Databases, platforms, metadata, security, backup, performance
Use and share	Access, integration, reporting, analytics, interoperability
Archive	Long-term retention, cost, retrieval needs, classification
Dispose	Authorized deletion or destruction when no longer needed

Exam trap: If a question asks for the best long-term solution, prefer lifecycle controls and prevention over repeated manual cleanup.

Common CDMP Wording Traps

Watch for these patterns when answering practice questions.

Wording pattern	What it often tests	Better approach
“Best first step”	Sequencing	Understand requirements, ownership, definitions, or impact before implementing tools
“Most responsible for”	Accountability	Distinguish owner, steward, custodian, architect, and consumer
“Enterprise-wide”	Governance or architecture	Avoid local project-only fixes
“Trusted data”	Quality, metadata, lineage, governance	Do not choose only storage or reporting
“Common definition”	Business glossary or metadata	Do not choose physical database design
“Duplicate customers”	MDM and data quality	Include matching, survivorship, stewardship
“Sensitive data exposure”	Security and governance	Include classification, access, monitoring, and handling rules
“Inconsistent reports”	Definitions, lineage, integration, quality	Avoid assuming the BI tool is the root cause
“Historical analysis”	Data warehousing/BI	Operational database is usually not the best answer
“Impact of a change”	Metadata and lineage	Need traceability across sources, transformations, and reports

Fast Decision Rules

Use these quick rules during topic drills and mock exams.

If the question emphasizes…	Think first about…
Accountability, ownership, decision rights	Data governance
Business definitions and shared terminology	Business glossary and metadata
Structure of business concepts	Conceptual or logical data modeling
Tables, indexes, partitions, datatypes	Physical design and operations
Data movement between systems	Integration and interoperability
Trusted entity records across systems	Master data management
Standard code lists	Reference data management
Reporting, history, dashboards, metrics	Data warehousing and BI
Meaning, lineage, discovery, impact analysis	Metadata management
Missing, invalid, duplicated, inconsistent data	Data quality management
Access, sensitivity, misuse, disclosure	Data security
Documents, records, versions, retention	Content and records management
Large-scale analytics or ML	Big data, data science, and analytics governance

What Strong Candidates Can Explain

Before moving into mixed mock exams, make sure you can explain these without looking them up:

The difference between data governance, data management, and data stewardship.
Why data owners are accountable for business meaning while custodians often manage technical environments.
The difference between conceptual, logical, and physical data models.
Why reference data and master data are related but not the same.
How metadata supports lineage, impact analysis, quality, governance, and discovery.
Why data quality is “fitness for use,” not abstract perfection.
The difference between profiling, cleansing, monitoring, and root-cause prevention.
Why data warehousing supports analytics differently from operational systems.
How ETL, ELT, APIs, replication, streaming, and virtualization differ.
Why security requires classification, access control, monitoring, and accountability.
How lifecycle thinking changes retention, archiving, and disposal decisions.
Why tool selection is rarely the best first answer when governance, definitions, or requirements are unclear.

Review-to-Practice Plan

Use this Quick Review as a bridge into IT Mastery practice.

Step 1: Diagnose by Topic

Start with short topic drills from an original question bank. Do not begin with only full mock exams unless you already know your weak areas.

Recommended drill order:

Data governance and stewardship
Data modeling and architecture
Metadata and data quality
Reference data and master data
Integration and interoperability
Data warehousing and BI
Security, lifecycle, storage, and operations
Content management, big data, and data science

Step 2: Read Detailed Explanations Carefully

For every missed or guessed question, identify the reason:

Miss reason	What to do
Term confusion	Build a short contrast table
Role confusion	Review owner, steward, custodian, architect, and consumer responsibilities
Sequencing error	Ask what should happen before implementation
Tool-first thinking	Reframe the issue as governance, quality, metadata, or lifecycle
Overlooking wording	Highlight “first,” “best,” “most responsible,” and “enterprise-wide”
Weak domain knowledge	Return to targeted topic drills before another mock exam

Step 3: Move to Mixed Practice

After topic drills, use mixed question sets to practice switching domains quickly. The real challenge is often recognizing which knowledge area a scenario belongs to.

Step 4: Use Mock Exams for Timing and Judgment

Mock exams are most useful after you have already corrected major topic gaps. Review detailed explanations for both incorrect and correct answers, especially when you chose correctly by guessing.

Final Rapid Check

Before your next practice session, ask yourself:

Is this problem about governance, management, architecture, quality, metadata, or security?
Who is accountable for the data decision?
Is the issue caused by unclear definitions, poor quality, weak controls, or bad integration?
Does the answer solve the root cause or only clean up symptoms?
Is the question asking for a strategic, tactical, or operational response?
Would a business stakeholder, steward, architect, custodian, or analyst be the right lead?
Is the answer enterprise-reusable or only a local workaround?

Practical Next Step

Use this Quick Review to choose your weakest two or three CDMP topics, then work through focused topic drills with original practice questions and detailed explanations before attempting a full mixed mock exam.

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.

Study Plan