DAMA CDMP Data Governance Specialist Quick Reference

Last revised: June 25, 2026

Compact exam-prep reference for DAMA International CDMP Governance data governance concepts, roles, controls, artifacts, and decision points.

Exam Identity

Item	Detail
Vendor/provider	DAMA International
Official exam title	DAMA CDMP Data Governance Specialist
Official exam code	CDMP Governance
Page purpose	Independent Quick Reference for focused review and practice support

Core Data Governance Definition

Data governance is the exercise of authority, control, and shared decision-making over data assets. It defines who can make which decisions about data, under what rules, using which processes, with what accountability.

Concept	Exam-useful meaning
Data governance	Decision rights, accountability, policy, oversight, and control for data assets
Data management	Execution of practices that plan, build, operate, protect, and improve data assets
Data stewardship	Formal accountability for data definition, quality, usage, and issue resolution
Data ownership	Business accountability for data meaning, value, risk, and authorized use
Data custodianship	Technical responsibility for storage, processing, backup, access enablement, and operations
Data policy	High-level statement of required behavior or control
Data standard	Specific rule or convention that supports a policy
Data procedure	Step-by-step method for performing governance or management work
Data control	Mechanism used to prevent, detect, or correct noncompliance, risk, or poor quality

High-Yield Distinctions

Distinction	Remember this
Governance vs management	Governance decides, directs, prioritizes, and monitors; management executes and operates.
Owner vs steward	Owner has business accountability and decision authority; steward performs ongoing coordination, definition, quality, and issue work.
Policy vs standard	Policy says what must be true; standard says how it must be implemented or measured.
Accountability vs responsibility	Accountability is answerability for outcomes; responsibility is performing assigned work.
Data governance vs data quality	Governance defines accountability, rules, and escalation; data quality applies profiling, monitoring, remediation, and prevention.
Data governance vs metadata management	Governance requires trusted definitions and lineage; metadata management captures, manages, and publishes that knowledge.
Data governance vs security	Governance sets rules for acceptable data use and access accountability; security enforces confidentiality, integrity, and availability controls.
Centralized vs federated governance	Centralized maximizes consistency; federated balances enterprise standards with domain-level ownership.
Compliance vs value	Compliance is one driver; governance also improves trust, reuse, efficiency, analytics, and decision quality.
Committee vs stewardship	Committees make decisions and resolve escalations; stewards do working-level coordination and control execution.

Data Governance Purpose and Drivers

Driver	Governance response
Regulatory or contractual risk	Policies, controls, accountability, evidence, retention, privacy, auditability
Poor data quality	Stewardship, definitions, quality rules, issue workflow, root-cause remediation
Conflicting definitions	Business glossary, authoritative definitions, data ownership, metadata standards
Siloed data	Enterprise principles, shared standards, master/reference data governance
Analytics inconsistency	Certified data sources, lineage, semantic consistency, quality thresholds
Digital transformation	Data product accountability, domain stewardship, platform standards
Mergers or reorganization	Data inventory, harmonized definitions, ownership reassignment, migration controls
Security and privacy exposure	Classification, access governance, acceptable use, data handling standards

Governance Operating Model Choices

Model	Best fit	Strengths	Risks / traps
Centralized	Highly regulated, enterprise-wide standardization needed	Consistency, strong policy control, clear escalation	Can become slow or disconnected from local business needs
Decentralized	Independent business units with limited data sharing	Local agility, domain knowledge	Inconsistent definitions, duplicate controls, weak enterprise reuse
Federated	Most large enterprises with shared and domain-specific data	Balances enterprise rules with domain ownership	Requires clear decision rights and escalation paths
Hybrid	Transition state or varied maturity across domains	Flexible adoption	Can be ambiguous if roles are not documented
Data-domain aligned	Customer, product, supplier, finance, employee, etc.	Assigns accountability by meaning and usage	Domains must be defined carefully to avoid overlap
Data-product aligned	Analytics, platform, or mesh-style operating models	Strong ownership of published data outputs	Needs explicit quality, metadata, and lifecycle obligations

Governance Role Reference

Role	Primary accountability	Common exam clues
Executive sponsor	Authority, funding, strategic alignment, issue escalation	Removes barriers; connects governance to business objectives
Data governance council / board	Approves policies, priorities, standards, and escalated decisions	Cross-functional decision-making body
Chief data officer / data leader	Enterprise data strategy, governance program leadership, value realization	Aligns governance with data management capabilities
Data owner	Business accountability for a data domain or critical data element	Approves definitions, quality expectations, and access rules
Data steward	Operational coordination of definitions, quality, issues, metadata, and standards	Maintains glossary entries, raises issues, supports controls
Data custodian	Technical operations and control implementation	Database/platform/file/storage administration
Data architect	Data models, integration patterns, standards alignment	Ensures structure supports enterprise principles
Data quality analyst	Profiling, rules, monitoring, defect analysis	Measures and reports data quality
Security/privacy officer	Classification, access, privacy, risk controls	Ensures protection and compliant handling
Business process owner	Process-level data creation and usage accountability	Important when root cause is process behavior
Project/product team	Implements governance requirements in change delivery	Must follow standards, metadata, and control requirements

RACI Pattern for Common Governance Activities

Activity	Executive sponsor	Governance council	Data owner	Data steward	Custodian / IT	Security / privacy
Approve enterprise data policy	A	R	C	C	C	C
Define critical data element	C	C	A	R	C	C
Approve business definition	C	C	A	R	C	C
Implement access control	C	C	A/C	C	R	A/R
Resolve cross-domain definition conflict	C	A/R	R	R	C	C
Monitor data quality rule	I	I	A	R	R/C	C
Remediate root cause in business process	C	C	A/R	R/C	C	C
Maintain technical metadata	I	I	C	C	A/R	C
Approve retention requirement	C	C	A/C	C	R/C	A/R
Report governance metrics	I	A	R/C	R	C	C

Legend: A = accountable, R = responsible, C = consulted, I = informed. Exact assignments vary by organization; exam questions usually test accountability logic, not one fixed chart.

Key Governance Artifacts

Artifact	Purpose	Common contents
Data governance charter	Establishes mandate, scope, authority, and objectives	Vision, goals, principles, roles, decision rights, governance bodies
Data policy	Defines required behavior for data handling or management	Ownership, quality, access, classification, retention, metadata, usage
Data standards	Translate policy into implementable rules	Naming, modeling, quality thresholds, metadata fields, code sets
Data governance roadmap	Sequences capability buildout	Initiatives, dependencies, milestones, maturity targets
Data domain model	Defines major subject areas of accountability	Customer, product, supplier, employee, location, financial data
Data ownership matrix	Assigns accountable owners and stewards	Domain, owner, steward, systems, critical elements
Business glossary	Shared business terms and definitions	Term, definition, owner, steward, synonyms, usage notes
Data catalog	Inventory and searchable metadata repository	Datasets, lineage, classification, quality indicators, owners
Critical data element list	Focuses control on high-value or high-risk data	Name, definition, source, owner, quality rules, controls
Data quality rules	Defines measurable expectations	Completeness, validity, consistency, accuracy, timeliness, uniqueness
Issue log	Tracks defects, decisions, and remediation	Issue, severity, owner, root cause, action, status
Decision log	Preserves governance decisions and rationale	Decision, date, participants, impact, policy reference
Data lineage map	Shows origin, movement, transformation, and usage	Source-to-target flows, transformations, reports, controls
Data classification scheme	Categorizes sensitivity, risk, and handling needs	Public/internal/confidential/restricted or equivalent levels
Control evidence	Demonstrates that governance controls operate	Approvals, reviews, audit logs, attestations, metrics

Data Governance Process Reference

Phase	Key actions	Outputs
Initiate	Identify drivers, sponsorship, scope, pain points, stakeholders	Charter, business case, initial scope
Assess	Evaluate maturity, risks, data issues, existing controls	Current-state assessment, gap analysis
Design	Define operating model, roles, policies, decision rights	Governance framework, role model, policy set
Prioritize	Select domains, critical data, initiatives, and metrics	Roadmap, backlog, domain priorities
Implement	Establish stewardship, standards, catalog/glossary, workflows	Working committees, artifacts, tools, controls
Operate	Run issue management, approvals, monitoring, escalation	Decisions, issue resolution, metrics
Monitor	Measure adoption, quality, compliance, and value	Dashboards, control evidence, maturity updates
Improve	Refine policies, automate controls, expand coverage	Lessons learned, enhanced standards, new capabilities

Governance Decision Rights

Decision type	Typical decision owner	Example
Policy decision	Governance council or executive authority	Approve enterprise data classification policy
Domain decision	Data owner with steward support	Define “active customer” for the customer domain
Standards decision	Governance function, architecture, or council	Adopt naming standard for data elements
Quality decision	Data owner, steward, quality lead	Set acceptable completeness threshold for a critical field
Access decision	Data owner with security/privacy input	Approve access to confidential customer data
Architecture decision	Data architecture / architecture board	Select authoritative source pattern
Exception decision	Governance council or delegated authority	Temporarily allow nonstandard interface with compensating control
Escalation decision	Higher governance body	Resolve conflicting definitions across business units

Policy, Standard, Procedure, and Guideline

Document type	Authority level	Example	Exam trap
Policy	Mandatory, high-level	“Customer personal data must be classified and protected.”	Do not confuse with step-by-step instructions.
Standard	Mandatory, specific	“Customer ID must be numeric and unique across source systems.”	More precise than policy.
Procedure	Mandatory process steps	“To request access, submit request, obtain owner approval, log ticket.”	Operationalizes policy/standard.
Guideline	Recommended practice	“Use plain-language business definitions where possible.”	Usually advisory unless adopted as required.
Principle	Stable design belief	“Data is an enterprise asset.”	Guides decisions but may need policies to enforce.

Governance Domains and What to Control

Area	Governance focus	Typical controls
Data architecture	Alignment of data structures with business needs	Architecture review, modeling standards, authoritative source rules
Data modeling and design	Consistent representation of business concepts	Naming conventions, model review, definition approval
Data storage and operations	Reliable, secure, recoverable data platforms	Backup, recovery, access, retention, operational controls
Data security	Authorized and appropriate access	Classification, role-based access, least privilege, monitoring
Data integration	Controlled data movement and transformation	Interface standards, lineage, reconciliation, transformation rules
Document and content management	Governance of unstructured/semi-structured data	Retention, classification, versioning, legal hold support
Reference and master data	Shared, consistent core entities and code sets	Golden record rules, survivorship, stewardship workflows
Data warehousing and BI	Trusted reporting and analytics	Certified metrics, semantic standards, report lineage
Metadata	Meaning, context, lineage, and usage knowledge	Glossary, catalog, required metadata fields, ownership
Data quality	Fitness for purpose	Quality rules, profiling, scorecards, remediation workflow
Data ethics	Appropriate and responsible use	Usage review, fairness considerations, transparency, accountability

Critical Data Elements

Critical data elements are data elements important enough to require explicit governance because they affect business decisions, risk, operations, reporting, compliance, or customer outcomes.

Selection criterion	Example question
Regulatory or audit impact	Is this element used in required reporting or evidence?
Financial impact	Does an error affect revenue, cost, reserves, or valuation?
Customer or stakeholder impact	Could poor data harm customers or service delivery?
Operational dependency	Do key processes fail if this data is wrong or late?
Cross-system reuse	Is this element shared across many systems or reports?
Executive reporting	Does leadership use this value for decisions?
Privacy/security sensitivity	Does it identify, classify, or expose a person, account, or asset?

Data Stewardship Reference

Stewardship type	Focus	Typical responsibilities
Business data steward	Meaning and business use	Definitions, quality expectations, issue triage, business rules
Technical data steward	Technical metadata and implementation support	Source mappings, lineage, data structures, transformation details
Domain steward	A subject area such as customer or product	Cross-application consistency and domain issue resolution
Project steward	Governance compliance in a project	Ensures new/change work follows standards
Operational steward	Day-to-day data process support	Monitors queues, validates corrections, supports remediation
Enterprise steward	Cross-domain alignment	Harmonizes definitions and escalates conflicts

Data Quality Dimensions

Dimension	Meaning	Example control
Accuracy	Correctly represents real-world value	Validate address against trusted source
Completeness	Required values are present	Required fields populated for critical records
Consistency	Same value agrees across systems or contexts	Customer status matches master data
Timeliness	Available and current when needed	Daily feed received before reporting cutoff
Validity	Conforms to format, domain, or rule	Date is valid; code exists in reference table
Uniqueness	No inappropriate duplication	One active customer master record per entity
Integrity	Relationships are valid and preserved	Order references existing customer
Reasonableness	Value is plausible in context	Birth date is not in the future
Conformity	Follows required representation	Country code uses approved standard

Data Quality Governance Workflow

    flowchart TD
	    A[Profile or monitor data] --> B{Issue detected?}
	    B -- No --> C[Continue monitoring]
	    B -- Yes --> D[Log issue and assign steward]
	    D --> E[Assess severity and business impact]
	    E --> F[Identify root cause]
	    F --> G{Root cause type}
	    G --> H[Source process correction]
	    G --> I[System or integration fix]
	    G --> J[Definition or rule clarification]
	    H --> K[Implement remediation]
	    I --> K
	    J --> K
	    K --> L[Validate fix]
	    L --> M[Update metadata, rules, controls]
	    M --> N[Report metric and close]

Data Quality Issue Triage

If the issue is…	Likely response
Isolated bad record	Correct record, log cause if material
Recurring defect	Root-cause analysis and process/system remediation
Conflicting definitions	Escalate to owner/council for semantic decision
Missing ownership	Assign owner/steward before defining remediation
Unclear business rule	Document and approve rule before implementing validation
Technical mapping error	Fix transformation, update lineage and mapping metadata
Source process error	Change process, training, input controls, or upstream validation
Access-related correction delay	Review permissions and workflow accountability

Metadata and Glossary Governance

Asset	Governance purpose	Key exam clues
Business glossary	Shared business language	Terms, definitions, owners, synonyms, policies
Technical metadata	Physical implementation details	Tables, columns, data types, jobs, schemas
Operational metadata	Processing and runtime information	Load times, job status, volumes, errors
Lineage metadata	Movement and transformation visibility	Source-to-target path, transformations, downstream usage
Usage metadata	How data is consumed	Reports, queries, users, frequency
Classification metadata	Risk and handling requirements	Sensitivity level, privacy category, retention class
Quality metadata	Trust indicators	Quality rules, scores, exceptions, thresholds

Master and Reference Data Governance

Concept	Governance focus	Common decision points
Master data	Core business entities shared across processes	Customer, product, supplier, employee, location
Reference data	Permitted values or code sets	Country codes, status codes, product categories
Golden record	Best representation of an entity	Survivorship rules, matching, stewardship approval
System of record	Authoritative system for a data element or process	Ownership, integration, lineage
System of reference	Trusted source for lookup or reporting use	Publication and synchronization rules
Match/merge	Identifies duplicates and combines records	Thresholds, false positives, manual review
Survivorship	Selects winning values from sources	Source priority, recency, completeness
Hierarchy governance	Manages parent-child relationships	Approval, versioning, effective dating

Data Classification and Handling

Classification concern	Governance action
Sensitivity	Define classification levels and required handling
Privacy	Identify personal, confidential, or restricted attributes
Access	Require owner approval and role-appropriate permissions
Retention	Define how long data is kept and when disposed
Usage	Specify approved and prohibited uses
Sharing	Control internal/external transfer conditions
Masking or de-identification	Apply when lower-risk use is needed
Auditability	Retain evidence of approvals and access changes
Third-party use	Define contractual and control expectations

Risk, Compliance, and Control Reference

Governance risk	Preventive control	Detective control	Corrective control
Unauthorized access	Classification, approval workflow, least privilege	Access review, audit logs	Revoke access, remediate exposure
Inconsistent reporting	Certified metrics, glossary, semantic layer standards	Reconciliation, report inventory review	Retire duplicate reports, align definitions
Poor data quality	Input validation, stewardship, source controls	Profiling, scorecards, exception reports	Root-cause remediation, data correction
Uncontrolled data change	Change management, model review	Lineage impact analysis, change audit	Rollback, update mappings, communicate changes
Unknown data ownership	Ownership matrix, domain model	Ownership gap assessment	Assign owner/steward and document accountability
Excessive retention	Retention schedule, lifecycle controls	Storage review, aging reports	Dispose/archive according to policy
Unapproved data sharing	Sharing standards, contract review	Data transfer monitoring	Stop transfer, remediate, update controls
Metadata decay	Required metadata workflow	Catalog completeness metrics	Steward review and metadata refresh

Governance Metrics

Metric category	Example measures	What it indicates
Adoption	Number of governed domains, assigned owners, trained stewards	Program rollout and coverage
Policy compliance	Percentage of datasets with classification, access review completion	Control effectiveness
Metadata completeness	Required catalog fields populated, glossary approval status	Discoverability and accountability
Data quality	Defect rate, rule pass rate, issue aging, recurrence rate	Fitness for purpose and remediation success
Issue management	Open issues, severity, time to resolution, escalation count	Operational governance performance
Value	Reduced rework, improved reporting cycle time, fewer reconciliations	Business benefit
Risk reduction	Fewer unauthorized access exceptions, improved audit findings	Control and compliance impact
Stewardship effectiveness	Steward participation, decisions completed, backlog trend	Operating model health

Maturity Model Thinking

Maturity level	Characteristics	Governance priority
Ad hoc	Informal ownership, inconsistent definitions, reactive fixes	Establish sponsorship, scope, basic ownership
Repeatable	Some policies and stewards, inconsistent execution	Standardize processes and decision rights
Defined	Documented framework, domains, policies, workflows	Expand coverage and integrate with projects
Managed	Metrics, controls, monitoring, formal escalation	Improve effectiveness and automate evidence
Optimized	Continuous improvement, embedded governance, measurable value	Optimize value, reduce friction, adapt to change

Do not assume maturity is only about tools. Higher maturity means governance is embedded in decisions, processes, controls, and culture.

Implementation Roadmap Pattern

Step	Practical focus	Avoid this trap
1. Confirm business drivers	Tie governance to risk, value, quality, or strategy	Starting with a tool selection
2. Secure sponsorship	Obtain authority for decisions and conflict resolution	Treating governance as a data team-only activity
3. Define scope	Choose domains, data elements, and use cases	Trying to govern all data equally on day one
4. Assign roles	Name owners, stewards, councils, custodians	Assigning responsibility without authority
5. Establish policies	Create clear, enforceable expectations	Writing policies that no process can execute
6. Build artifacts	Glossary, catalog, quality rules, issue log	Creating documentation with no owner
7. Embed in processes	Projects, access, change, quality, reporting	Running governance as a separate meeting-only function
8. Measure and improve	Use metrics and feedback loops	Measuring activity only, not outcomes

Decision Matrix: What Governance Mechanism Fits?

Situation	Best mechanism
Business units disagree on a term	Data owner/steward analysis, council decision, glossary update
A dataset has unknown sensitivity	Classification standard and owner review
Report numbers do not match	Certified metric definition, lineage, reconciliation, quality rules
New project creates a shared data field	Architecture/model review, definition approval, metadata capture
Analysts cannot find trusted data	Data catalog, glossary, certified sources, ownership metadata
Access requests are inconsistent	Access policy, owner approval workflow, periodic access review
Duplicate customer records occur	Master data governance, match/merge rules, stewardship queue
Code values differ across systems	Reference data governance and synchronization process
Data quality fixes do not last	Root-cause remediation and source process controls
Data governance has low engagement	Link scope to business pain, clarify authority, show metrics

Governance in Change Delivery

Delivery activity	Governance requirement
Business requirements	Identify data owners, critical data, definitions, quality needs
Solution design	Apply architecture, integration, metadata, and security standards
Data modeling	Review naming, definitions, relationships, and authoritative sources
Data migration	Define mapping, profiling, cleansing, reconciliation, and signoff
Integration	Document lineage, transformation rules, controls, and monitoring
Testing	Include data quality, access, privacy, and reconciliation tests
Deployment	Ensure catalog/glossary updates and operational ownership
Post-implementation	Monitor quality, issues, adoption, and control effectiveness

Common Governance Anti-Patterns

Anti-pattern	Why it fails	Better approach
“Buy a catalog and call it governance”	Tools do not create authority or accountability	Define operating model, roles, policies, and workflows first
Govern everything equally	Resources are diluted	Prioritize critical data and high-value domains
IT-only ownership	Business meaning and accountability are missing	Assign business owners and stewards
Committee with no decision rights	Meetings produce discussion, not control	Document authority, escalation, and decision scope
Policy without enforcement	Behavior does not change	Attach controls, procedures, metrics, and consequences
Stewardship as a side job only	Work is under-resourced	Define expectations, time allocation, and management support
Metrics only on activity	Busy work may not create value	Include quality, risk, cycle time, adoption, and business impact
Ignoring culture	Users bypass controls	Communicate value and embed governance into normal work

High-Yield Scenario Cues

Scenario wording	Likely exam direction
“Who is accountable for the meaning of the data?”	Data owner, supported by steward
“Who maintains definitions and coordinates issue resolution?”	Data steward
“Who implements database access controls?”	Custodian / technical team, under policy and approval rules
“Conflicting definitions across business units”	Governance council or cross-domain decision process
“Need trusted reporting metrics”	Glossary, certified definitions, lineage, quality controls
“Repeated downstream defects”	Root-cause analysis at source process, not only downstream cleansing
“No one knows where data comes from”	Metadata and lineage management
“Sensitive data used for analytics”	Classification, access control, privacy review, approved use
“Duplicate master records”	Master data governance and stewardship workflow
“Governance program lacks authority”	Executive sponsorship and charter

Data Governance Principles

Principle	Practical implication
Data is an enterprise asset	Manage data for shared value, not only local application needs
Accountability must be explicit	Assign named owners/stewards and decision rights
Governance should be risk- and value-based	Focus strongest controls on critical, shared, sensitive, or high-impact data
Business and IT share responsibilities	Business owns meaning and value; IT enables technical management and controls
Definitions should be standardized where shared	Avoid conflicting metrics and semantic ambiguity
Quality must be measured against use	Fitness for purpose depends on business context
Metadata is a governance enabler	You cannot govern what you cannot find, define, or trace
Governance must be embedded	Controls should fit projects, operations, analytics, and access processes
Exceptions must be managed	Temporary deviations need approval, rationale, risk acceptance, and review
Continuous improvement matters	Governance matures through feedback, metrics, and adaptation

Quick Review Checklist

Before exam practice, make sure you can answer:

Who makes data decisions, who executes them, and who is accountable for outcomes?
How do policy, standard, procedure, control, and metric differ?
When should a governance council be used instead of a steward or owner?
How do data quality, metadata, master data, security, and architecture connect to governance?
What artifacts prove that governance is operating, not just documented?
How should governance prioritize domains, data elements, and issues?
What does a federated model solve, and what ambiguity can it create?
Why is root-cause remediation better than repeated downstream correction?
How do classification, access approval, retention, and usage rules reduce risk?
Which metrics show adoption, effectiveness, value, and control performance?

Final Exam-Prep Next Step

Use this Quick Reference to build scenario drills: for each practice question, identify the data asset, decision right, accountable role, governing artifact, control, and escalation path before selecting an answer. Then continue with targeted CDMP Governance practice questions focused on roles, operating models, stewardship, data quality, metadata, policy, and risk scenarios.

Scenario Guide

Data Governance Foundations and Principles