DAMA CDMP Data Governance Specialist Cheat Sheet

Last revised: September 16, 2026

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

Use the tables for a quick pre-exam check. Expand a topic’s notes for explanations, examples, and additional distinctions.

Scope and study context

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

Data governance questions often test whether you can distinguish decision rights, accountability, policy, stewardship, control, and value delivery from the operational work of managing data. Expect scenario-based questions where several answers sound reasonable, but only one best aligns with governance principles.

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

Notes and examples

Governance operating model

A data governance operating model defines how governance work is organized and performed.

Common components

Component	Purpose
Sponsorship	Provides authority, funding, priority, and executive support
Governance council or board	Makes cross-functional decisions, resolves escalations, approves policies and priorities
Data owners	Hold business accountability for data domains or critical data elements
Data stewards	Support definition, quality, metadata, issue management, and policy adoption
Data custodians	Implement and operate technical controls and platforms
Working groups	Address domain-specific issues, standards, definitions, and improvement plans
Policies and standards	Define required behavior and consistent expectations
Processes	Provide repeatable workflows for issues, changes, access, definitions, and exceptions
Metrics	Track adoption, performance, quality, compliance, and value

Centralized, decentralized, and federated models

Model	Description	Strength	Weakness
Centralized	A central team owns most governance decisions and standards	Consistency and control	May be slow or disconnected from business context
Decentralized	Business units govern data independently	Local responsiveness	Inconsistent definitions, controls, and priorities
Federated	Enterprise standards with domain-level participation and accountability	Balances consistency and local expertise	Requires clear roles, escalation, and coordination

For many enterprise scenarios, a federated model is often the best-fit concept because it recognizes that data is used across the enterprise but understood deeply by business domains.

Common operating model trap

A governance council should not be treated as the team that personally fixes every data problem. Its role is to prioritize, decide, assign accountability, remove barriers, and monitor outcomes.

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

Notes and examples

Role review table

Role	Main responsibility	Strong exam clue
Executive sponsor	Provides mandate, funding, visibility, and authority	Lack of adoption or cross-functional support
Chief Data Officer or equivalent leadership role	Leads enterprise data strategy and governance capability	Need for enterprise coordination and value realization
Data governance council	Approves policies, resolves conflicts, sets priorities	Cross-domain decision or escalation
Data owner	Business accountability for data domain, definition, quality expectations, and use	“Who is accountable?”
Data steward	Day-to-day support for data definitions, quality issues, metadata, and standards	“Who coordinates definitions or monitors quality?”
Data custodian	Technical implementation and care of data assets	Storage, backup, security configuration, system operation
Data user/consumer	Uses data appropriately according to policy and business need	Reporting, analytics, operational usage
Data producer	Creates or captures data	Upstream quality defects and process controls
Risk, legal, privacy, compliance	Interprets obligations and controls	Regulatory, retention, privacy, audit issues
IT/security	Implements platforms, access controls, and technical safeguards	Technical enablement and control enforcement

RACI thinking

Questions may describe a governance activity and ask who should be responsible or accountable. Use this logic:

Activity	Usually accountable	Usually responsible/supporting
Approving enterprise data policy	Governance council/executive authority	Data governance team, legal, compliance, security
Defining business meaning of a critical data element	Data owner	Data steward, subject matter experts
Maintaining metadata in a repository	Stewardship/data management function	Custodians, data architects, tool administrators
Implementing access control in a system	IT/security custodian	Data owner approves, security advises
Resolving conflict between business units	Governance council or escalation authority	Data owners, stewards, governance office
Monitoring data quality metrics	Data steward/data quality team	Data owner accountable for outcomes
Approving exception to policy	Defined governance authority	Risk, compliance, legal, business owner

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

Notes and examples

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.

Notes and examples

Policies, standards, procedures, and guidelines

The exam may test whether you understand the hierarchy of governance artifacts.

Artifact	Meaning	Example
Policy	Mandatory high-level rule	Customer personal data must be protected according to approved privacy and security requirements
Standard	Specific mandatory requirement supporting policy	Customer identifiers must follow an approved format and naming standard
Procedure	Step-by-step process	Steps to request access to restricted customer data
Guideline	Recommended practice	Preferred naming convention examples for analytics datasets
Control	Mechanism to enforce or monitor requirements	Approval workflow, access review, quality threshold, audit log

Decision rule

If the scenario involves a broad requirement that applies across the organization, choose policy. If it involves detailed uniform implementation requirements, choose standard. If it involves how to perform a task, choose procedure.

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?

Notes and examples

Critical data elements

A critical data element is a data element important enough to require special governance attention because it affects business operations, reporting, risk, regulatory obligations, customer experience, or strategic decisions.

What governance does for critical data elements

Governance action	Purpose
Identify and prioritize	Focus effort where risk or value is highest
Assign ownership and stewardship	Ensure accountability
Define business meaning	Reduce ambiguity
Document lineage	Understand origin, transformation, and downstream use
Set quality rules	Establish measurable expectations
Monitor quality	Detect and trend issues
Manage changes	Prevent unintended downstream impact
Control access and use	Protect sensitive or regulated data

Common trap

Not all data should receive the same governance intensity. Effective governance is risk-based and value-based. Applying heavy controls to every data element can create unnecessary cost and resistance.

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

Notes and examples

Data stewardship

Data stewardship is a key enabling function within governance. Stewards help ensure data is defined, understood, controlled, and improved.

Stewardship activities

Develop and maintain business definitions
Support data classification
Identify critical data elements
Document metadata and lineage
Monitor data quality rules and metrics
Coordinate issue investigation and remediation
Support data access and usage decisions
Facilitate alignment across business and technical teams
Promote policy and standard adoption

Types of stewards

Steward type	Focus
Business data steward	Business meaning, usage, rules, and quality expectations
Technical data steward	Technical metadata, lineage, data structures, and system implementation
Domain data steward	Data within a business domain, such as customer, product, supplier, or finance
Enterprise data steward	Cross-domain consistency, enterprise standards, and coordination
Data quality steward	Quality rules, monitoring, issue tracking, and remediation support

Stewardship trap

Stewardship is not just documentation. It is an accountability-support role that connects business meaning, operational processes, quality control, and governance decisions.

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

Notes and examples

Data quality governance

Data quality is a frequent data governance topic because governance defines who is accountable for quality, what “fit for purpose” means, and how quality issues are escalated.

Common data quality dimensions

Dimension	Question it answers
Accuracy	Does the data correctly represent the real-world object or event?
Completeness	Are required values present?
Consistency	Does data agree across systems or records?
Timeliness	Is data available and current when needed?
Validity	Does data conform to rules, formats, or allowed values?
Uniqueness	Are duplicates controlled?
Integrity	Are relationships valid and preserved?
Conformity	Does data follow approved standards?
Reasonableness	Are values plausible within business expectations?

Quality governance workflow

Identify critical data and business impact.
Define quality rules and thresholds.
Assign owner and steward accountability.
Profile and measure data.
Record issues and root causes.
Prioritize remediation by risk and value.
Implement process or system controls.
Monitor trends and report to governance bodies.

Quality trap

Fixing bad data downstream is usually less effective than addressing root causes at creation, capture, integration, or process handoff. In scenario questions, prefer answers that prevent recurrence rather than merely cleansing symptoms.

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

Notes and examples

Metadata governance

Metadata is data about data. Governance uses metadata to create shared understanding, traceability, and control.

Metadata types

Metadata type	Examples	Governance value
Business metadata	Definitions, business rules, owners, classifications	Common meaning and accountability
Technical metadata	Table names, columns, data types, mappings, interfaces	Implementation transparency
Operational metadata	Batch runs, job status, usage, refresh time, error logs	Monitoring and service management
Process metadata	Workflow steps, approvals, lifecycle status	Governance process control
Lineage metadata	Source-to-target flow, transformations, dependencies	Impact analysis and trust

High-yield metadata concepts

A business glossary supports shared meaning.
A data catalog helps users discover and understand data assets.
Lineage supports impact analysis, auditability, quality investigation, and trust.
Metadata quality matters; a stale catalog can reduce confidence.
Governance defines metadata standards, ownership, required fields, and maintenance processes.

Metadata trap

A tool does not create governance by itself. A catalog or glossary only works when roles, processes, standards, and accountability are in place.

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

Notes and examples

Reference data and master data governance

Reference data and master data frequently require strong governance because they are reused across systems and business processes.

Reference data

Reference data consists of permissible values used to classify or categorize other data.

Examples:

Country codes
Currency codes
Product categories
Status codes
Business unit codes

Governance focus:

Approved value lists
Change control
Authoritative sources
Versioning
Consistency across systems

Master data

Master data represents core business entities shared across processes.

Customer
Product
Supplier
Employee
Location
Account
Authoritative source or system of record
Survivorship rules
Duplicate management
Identity resolution
Business definitions
Cross-functional ownership
Data quality monitoring

Exam trap

A master data program is not just a technology implementation. Master data success depends on governance: ownership, standards, definitions, matching rules, stewardship, change management, and issue resolution.

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

Notes and examples

Data governance metrics

Metrics show whether governance is adopted, effective, and valuable. Avoid relying only on activity metrics; include outcome and value measures.

Metric categories

Category	Examples	What it tells you
Adoption	Number of governed domains, steward participation, policy acknowledgment	Whether governance is being used
Data quality	Defect rates, completeness, duplicate rate, rule pass rate	Whether data is improving
Issue management	Open issues, aging, resolution time, recurrence	Whether problems are being controlled
Metadata	Catalog coverage, glossary completeness, lineage availability	Whether data is understandable
Access and compliance	Access review completion, exceptions, audit findings	Whether controls are working
Business value	Reduced rework, faster reporting, fewer reconciliations, improved decision confidence	Whether governance supports outcomes
Maturity	Capability assessment results over time	Whether the program is improving

Metric trap

Counting meetings, policies, or stewards does not prove governance effectiveness. Prefer metrics linked to reduced risk, improved quality, better decisions, adoption, and measurable business outcomes.

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

Cheat Sheet 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?

Notes and examples

Rapid review checklist

Before taking a practice set, confirm that you can explain:

What data governance is and why it matters
How governance differs from data management
How owners, stewards, custodians, sponsors, and councils interact
Why executive sponsorship is important
How policies, standards, procedures, guidelines, and controls differ
How critical data elements are identified and governed
How governance supports data quality improvement
Why metadata, glossary, catalog, and lineage matter
How classification influences access, privacy, security, retention, and use
How governance applies to master and reference data
How issue management and escalation should work
How governance metrics should show adoption, risk reduction, quality improvement, and value
Why change management and communication are essential
How to choose proportionate governance based on risk and value

Final Exam-Prep Next Step

Use this Cheat Sheet 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.

Core idea: what data governance is

Data governance is the system of authority, accountability, policies, decision rights, controls, and oversight that enables an organization to manage data as an asset.

It answers questions such as:

Who has authority to define, approve, change, or retire data rules?
Who is accountable for data quality, meaning, access, retention, and use?
Which policies and standards apply across business units?
How are conflicts resolved when stakeholders disagree?
How is compliance, risk reduction, and business value measured?
How do data management practices align with organizational strategy?

Notes and examples

Governance versus management

Concept	Primary focus	Typical activities	Exam trap
Data governance	Decision rights, accountability, oversight	Approving policies, assigning stewardship, resolving cross-functional issues, setting standards	Confusing governance with hands-on technical data work
Data management	Execution and operation	Profiling data, building data models, maintaining metadata repositories, configuring tools	Treating operational tasks as the governance body’s main job
Data stewardship	Accountable care of data on behalf of the organization	Defining terms, reviewing quality issues, supporting policy adoption	Assuming stewards “own” all data or replace business accountability
Data ownership/accountability	Business responsibility for data meaning, use, and risk	Approving definitions, access rules, quality expectations	Assuming IT is the default owner because it stores data
Data custodianship	Technical care and safeguarding	Storage, backups, access implementation, platform operations	Confusing custody with business ownership

A useful exam decision rule:

If the question is about who decides, who is accountable, what policy applies, or how conflicts are escalated, think data governance. If the question is about how work is technically performed, think data management execution.

High-yield governance objectives

Data governance exists to improve business outcomes, not to create bureaucracy. Common objectives include:

Objective	What it means in exam scenarios
Strategic alignment	Data priorities support business strategy, regulatory obligations, and enterprise goals
Accountability	Named roles are responsible for definitions, quality, access, compliance, and issue resolution
Consistency	Shared policies, standards, definitions, and decision processes reduce local variation
Risk management	Data risks are identified, controlled, monitored, and escalated
Data quality improvement	Quality expectations are defined, measured, and acted on
Regulatory and policy compliance	Data handling supports privacy, security, retention, audit, and legal obligations
Value realization	Governance enables better analytics, operations, customer experience, and decision-making
Transparency	Stakeholders can understand data meaning, lineage, quality, and permitted use

Data governance and the DAMA knowledge areas

Data governance interacts with every major data management discipline. A specialist-level candidate should understand the relationships.

Data management area	Governance connection
Data architecture	Governance sets principles and standards for data structures, integration, and enterprise alignment
Data modeling and design	Governance supports naming, definitions, relationships, and modeling standards
Data storage and operations	Governance defines retention, protection, availability, and operational expectations
Data security	Governance defines access accountability, classification, acceptable use, and control expectations
Data integration and interoperability	Governance promotes shared definitions, lineage, interface standards, and data movement controls
Documents and content	Governance addresses unstructured data, records, retention, classification, and ownership
Reference and master data	Governance defines authoritative sources, stewardship, quality, and change control
Data warehousing and business intelligence	Governance supports trusted metrics, semantic consistency, lineage, and report certification
Metadata	Governance requires business, technical, and operational metadata for transparency
Data quality	Governance defines dimensions, thresholds, accountability, measurement, and remediation
Big data and analytics	Governance addresses ethical use, model risk, lineage, privacy, quality, and reproducibility

Data classification, access, privacy, and security

Data governance and data security are closely connected. Governance defines expectations and accountability; security implements and monitors technical controls.

Classification review

Classification concept	Governance purpose
Public, internal, confidential, restricted, or similar levels	Match protection to sensitivity and risk
Personal data or sensitive personal data	Trigger privacy, consent, access, and minimization considerations
Financial, health, legal, or regulated data	Identify special handling and audit needs
Intellectual property	Protect business value and competitive advantage
Retention category	Control how long data is kept and when it is disposed

Notes and examples

Access governance principles

Principle	Meaning
Least privilege	Users receive only the access needed for approved work
Need to know	Access is tied to legitimate business purpose
Segregation of duties	Avoid conflicting access that increases fraud or misuse risk
Approval accountability	Business owners approve access based on data sensitivity and use
Periodic review	Access rights are reviewed and recertified
Auditability	Access decisions and activity can be traced

Privacy and ethical use

Governance should address:

Purpose limitation
Appropriate access
Data minimization
Consent or permitted use where applicable
Retention and disposal
Transparency
Protection of sensitive data
Ethical analytics and responsible data use

Security trap

Do not choose an answer that makes IT solely responsible for data access decisions. IT often implements access, but business accountability and governance-approved policies determine who should have access and why.

Data lifecycle governance

Data governance should cover the full data lifecycle.

Lifecycle stage	Governance concerns
Plan	Business purpose, accountability, standards, risk assessment
Create/capture	Quality at source, validation, metadata, consent or permitted use
Store	Security, classification, retention, backup, availability
Use/share	Access, usage rights, interpretation, quality, lineage
Integrate/transform	Mapping, reconciliation, lineage, control checks
Archive	Retention, retrieval, legal hold, cost management
Dispose	Secure deletion, defensible disposal, audit evidence

Lifecycle trap

Retention and disposal are governance issues, not merely storage issues. Keeping data indefinitely can increase cost, risk, and compliance exposure.

Governance processes candidates should recognize

Common processes

Process	Purpose	Key outputs
Policy management	Create, approve, communicate, and maintain policies	Approved policies, standards, exception rules
Data issue management	Capture, prioritize, assign, resolve, and monitor issues	Issue log, root cause, remediation plan
Data definition management	Establish and maintain approved business terms	Glossary entries, definitions, synonyms
Data quality management	Define, measure, monitor, and improve quality	Rules, scorecards, thresholds, trends
Data access management	Approve and review data access	Access approvals, recertification evidence
Data classification	Identify sensitivity and handling needs	Classification labels, protection requirements
Metadata management	Capture and maintain metadata	Catalog, lineage, ownership, technical mappings
Change management	Assess and control changes to data, definitions, systems, or reports	Impact assessment, approvals, communication
Exception management	Allow controlled deviation from policy	Risk acceptance, expiration, approval record
Maturity assessment	Evaluate governance capability and improvement roadmap	Maturity scores, gaps, action plan

Notes and examples

Issue escalation path

    flowchart TD
	    A[Data issue identified] --> B[Log issue with impact and evidence]
	    B --> C{Can domain steward resolve?}
	    C -- Yes --> D[Assign fix and monitor outcome]
	    C -- No --> E[Escalate to data owner]
	    E --> F{Cross-domain conflict or policy decision?}
	    F -- No --> D
	    F -- Yes --> G[Governance council decision]
	    G --> H[Implement remediation or policy change]
	    H --> I[Measure and report results]

Maturity and implementation

Data governance programs usually evolve over time. A maturity assessment helps identify current capability, target state, gaps, and roadmap priorities.

Typical maturity progression

Stage	Characteristics
Ad hoc	Inconsistent definitions, unclear ownership, reactive issue handling
Repeatable	Some local processes and stewards exist, but enterprise alignment is limited
Defined	Policies, roles, standards, and processes are documented and communicated
Managed	Metrics, controls, escalation, and monitoring are active
Optimized	Continuous improvement, automation, enterprise adoption, measurable value

Notes and examples

Do not assume every organization should immediately pursue maximum maturity in every area. A better answer usually aligns maturity goals with business strategy, risk, regulatory needs, and value.

Implementation success factors

Executive sponsorship
Clear business case
Prioritized scope
Defined decision rights
Practical policies and standards
Business participation
Stewardship network
Communication and training
Tooling that supports—not replaces—process
Metrics and continuous improvement
Change management and adoption planning

Implementation trap

A “big bang” enterprise rollout without prioritization, sponsorship, and adoption planning is usually risky. Exam scenarios often favor starting with high-value or high-risk domains, demonstrating results, and scaling.

Governance decision rules for exam scenarios

Use these rules when answer choices are close.

Scenario clue	Strong answer direction
Multiple departments define the same term differently	Establish approved business definition through governance/stewardship
Data quality defects recur	Identify root cause and assign accountable owner; improve process controls
Users cannot trust reports	Address lineage, definitions, quality rules, certification, and ownership
Sensitive data is broadly accessible	Classify data, enforce access governance, approve by owner, review access
New analytics project wants all available data	Apply purpose, classification, privacy, minimization, and approved use
System change may affect reports	Perform lineage and impact analysis before implementation
Business units disagree on standard values	Escalate through governance decision rights and approved standards
Glossary exists but is not used	Improve adoption, ownership, integration into processes, and communication
Governance is viewed as bureaucracy	Connect governance to business outcomes, risk reduction, and measurable value
IT is asked to define business meaning	Business owner/steward should define meaning; IT supports implementation

Common candidate mistakes

Mistake 1: Treating data governance as a technology project

Tools can support catalogs, workflow, lineage, quality monitoring, and access reviews. But governance requires authority, accountability, policies, roles, and decisions.

Better framing: people, process, policy, accountability, and technology together.

Mistake 2: Assuming the data governance team owns all data

The governance function coordinates and enables governance. Business data owners retain accountability for data meaning, quality expectations, and acceptable use.

Mistake 3: Choosing the fastest fix instead of the governed fix

A quick technical correction may not solve root cause, ownership, policy, or control gaps. In exam scenarios, choose sustainable remediation.

Mistake 4: Confusing “data owner” with “system owner”

A system owner may manage an application. A data owner is accountable for data as a business asset, especially meaning, quality, risk, and use.

Mistake 5: Ignoring change management

Governance fails when stakeholders do not understand roles, incentives, workflows, or benefits. Communication, training, and adoption are often the best answer.

Mistake 6: Over-governing low-risk data

Governance should be proportionate. Prioritize critical data, sensitive data, regulatory data, high-value analytics, and enterprise-shared data.

Mistake 7: Focusing only on compliance

Compliance is important, but governance also supports value creation, decision quality, operational efficiency, and strategic alignment.

Quick concept comparisons

Data owner versus data steward

Question	Data owner	Data steward
Main role	Accountable decision-maker	Operational governance support
Focus	Business accountability and authority	Definition, quality, metadata, coordination
Approves key decisions?	Usually yes	Usually recommends or prepares
Handles daily governance tasks?	Not usually	Often yes
Replaces IT?	No	No

Notes and examples

Policy versus standard versus procedure

If the question asks…	Think…
“What rule must everyone follow?”	Policy
“What exact requirement supports the rule?”	Standard
“What steps do we take?”	Procedure
“What is recommended?”	Guideline
“How do we enforce or test it?”	Control

Data governance versus data quality

Data governance	Data quality
Defines accountability, rules, priorities, and oversight	Measures and improves fitness for use
Establishes ownership and escalation	Identifies defects and root causes
Approves policies and standards	Applies rules, profiling, monitoring, remediation
Ensures quality is managed as a business issue	Provides evidence and improvement actions

Scenario mini-drills

Use these quick drills to test whether you are applying governance logic rather than memorizing definitions.

Drill 1

A finance report and a sales dashboard use different definitions of “active customer.” Executives are debating which number is correct.

Best governance response:

Assign business ownership for the term.
Use stewardship to document candidate definitions and usage.
Approve an enterprise or context-specific definition through the appropriate governance body.
Update glossary, lineage, reporting standards, and affected reports.

Notes and examples

Avoid: asking IT to choose the definition based only on current system logic.

Drill 2

A customer dataset has repeated address defects. Analysts clean the file every month before reporting.

Measure the defect pattern.
Determine root cause at capture, integration, or source process.
Assign accountable data owner and steward.
Implement validation or process controls upstream.
Monitor quality metrics and recurrence.

Avoid: continuing manual cleansing as the primary control.

Drill 3

A new analytics team requests unrestricted access to detailed personal data “in case it becomes useful.”

Confirm business purpose and approved use.
Apply classification and privacy/security requirements.
Use least privilege and minimization.
Approve access through accountable data owner and security process.
Monitor and review access.

Avoid: broad access without purpose, classification, or approval.

Drill 4

A data catalog has been purchased, but business users still do not trust the data.

Assign ownership and stewardship for catalog content.
Define required metadata and quality standards.
Link glossary terms, lineage, quality indicators, and certified assets.
Integrate catalog use into reporting, analytics, and change processes.
Measure adoption and usefulness.

Avoid: assuming tool deployment alone solves trust.

Put the review into practice

Study Plan