Data Owner
Approves standards, thresholds and priorities; remains accountable for the business data domain.
See how a concept becomes exam-ready.
Go beyond a definition. Follow a real Data Governance lesson from the core idea, through a visual model and a banking scenario, to the reasoning an exam question is testing.
Data GovernanceHigh emphasis in the companionChapter learning preview
The learning sequence
One concept. Four layers of understanding.
Each chapter is designed to help you orient yourself, understand the relationships, apply the idea and recall the distinction under exam pressure.
01 · ORIENT
Why it matters
Start with the purpose of the knowledge area and where it fits in the wider data-management discipline.
02 · UNDERSTAND
See the model
Use diagrams, role distinctions and structured explanations to connect the moving parts.
03 · APPLY
Work the scenario
Translate the concept into a realistic business or banking situation.
04 · RECALL
Recognise the exam cue
Identify the verb, the decision right and the common distractor before choosing an answer.
01 · Start with the idea
Governance decides. Management delivers.
Data Governance is the exercise of authority, control and shared decision-making over the management of data assets. It clarifies who has the right to decide, who is accountable, which policies apply and how disputes are resolved.
That distinction matters because a technically successful data activity can still fail as an enterprise practice if no one has the authority to set standards, resolve ownership disputes or enforce common rules.
The distinction to remember Governance establishes the rules and decision rights. Management performs the work: cleansing records, building pipelines, operating platforms and producing reports.
Where it fits in the wider discipline
In the DAMA-DMBOK wheel, Data Governance sits at the centre. It provides policy, roles, decision rights and escalation across the other knowledge areas. It does not replace those disciplines; it gives them an accountable operating framework.
A chapter diagram, restyled with the companion's navy, blue and white palette. The hub is Data Governance; the surrounding disciplines operate within its policy and decision framework.
02 · Understand the roles
Owner, Steward and Custodian: three responsibilities that are easy to confuse.
The exam often describes an action and asks which role should perform it. The reliable way through is to identify whether the action is about accountability, day-to-day business responsibility or technical operation.
The chapter's role diagram: accountable business ownership, responsible operational stewardship and technical custody are distinct but connected.
Data Steward
Defines and maintains business rules, monitors quality and coordinates day-to-day issue resolution.
Data Custodian
Operates and secures the platform that stores and processes the data, including technical access and backup controls.
“Approves / signs off”Think Data Owner
“Defines / monitors / resolves”Think Data Steward
“Stores / backs up / provisions”Think Data Custodian
03 · Apply it to a banking scenario
A customer definition is disputed across business units.
Retail Banking and Wealth Management use different definitions of “active customer”. The difference affects a group-level regulatory report. The data stewards have documented both definitions, but neither domain will accept the other's position.
What happens next? This is no longer a routine glossary-maintenance task. It is a cross-domain decision-rights issue that needs governance escalation. The appropriate governance body arbitrates; accountable data owners approve the outcome; stewards update and operationalise the agreed definition.
04 · The exam lens
Read the action before you read the options.
Scenario questions often contain several plausible roles. Ignore job titles at first and classify the verb:
- Approve: who has business accountability?
- Define and maintain: who performs the operational stewardship?
- Configure and operate: who has technical custody?
- Arbitrate cross-domain policy: which governance body has the mandate?
Common trap Do not assign an enterprise decision to the person who happens to maintain the glossary or administer the database. Operational proximity is not the same as decision authority.
Check your judgement
A short scenario challenge
A data steward identifies that a proposed customer-risk threshold would materially change the bank's risk appetite. Which action is most appropriate?
Beyond this preview
The full chapter keeps building.
This public lesson is an introduction to the approach. The companion's chapter goes further into the framework, operating models, policy hierarchy, governance bodies, common traps and revision.
19 structured concepts
From governance foundations and roles to councils, federated models and policy architecture.
Exam cues and common traps
Learn what the question is testing, why tempting alternatives are wrong and which distinctions to retain.
Purpose-built revision material
Consolidate critical definitions, role distinctions, policy sequences and last-mile reminders.
Independent CDMP preparation material. This demonstration is not official DAMA exam content and Data Shawarma is not affiliated with or endorsed by DAMA International.