Free DAMA CDMP Governance Practice Questions: Roles Responsibilities and Decision Rights

Topic snapshot

Sample questions

These are original IT Mastery practice questions aligned to this topic area. They are not official exam questions, copied live-exam content, or exam dumps. Use them for self-assessment, scope review, and deciding what to drill next.

Question 1

Topic: Roles Responsibilities and Decision Rights

A global retailer has named data stewards in each business domain. Glossary definitions, issue triage, and quality-rule proposals are handled differently by each domain, so adoption is uneven and cross-domain conflicts recur. Which stewardship practice would best improve consistency, adoption, collaboration, and sustainable governance operations?

Options:

• A. Require the data governance council to approve every glossary update

• B. Create a steward community of practice with shared playbooks and regular forums

• C. Ask each project manager to define stewardship tasks per project

• D. Move stewardship tasks to the central metadata administration team

Best answer: B

Explanation: A stewardship community of practice is the strongest fit when distributed stewards need consistent methods and sustained adoption. It supports shared templates, common issue and definition workflows, onboarding, peer review, and regular cross-domain coordination. This keeps accountability close to business domains while giving stewards a repeatable operating rhythm. It also reduces dependency on one central team and helps stewardship become an ongoing governance capability rather than a project-by-project activity. Council escalation remains important for unresolved decision-right conflicts, but routine consistency and collaboration are better handled through an active steward network.

• Council approval for everything creates a bottleneck and uses senior decision forums for routine stewardship work.
• Central metadata administration confuses tool or repository maintenance with business stewardship accountability.
• Project-defined tasks may help delivery teams, but it reinforces inconsistent practices across domains.

Question 2

Topic: Roles Responsibilities and Decision Rights

A sales analytics team asks several experienced regional analysts to “own” customer segment data because they often fix segment values before monthly reporting. The governance council wants the stewardship network to reduce recurring issues without turning informal cleanup into unclear accountability. What should the council do?

Options:

• A. Create a one-time project to cleanse all segment values

• B. Assign database administrators as segment data owners

• C. Let the analysts continue cleanup as volunteer subject-matter experts

• D. Appoint formal data stewards with defined responsibilities and escalation paths

Best answer: D

Explanation: Data stewardship is a formal governance role, not simply the person who knows the data or fixes defects before reports are published. In this situation, recurring quality problems require named stewardship responsibilities, agreed decision rights, documented procedures, and a route for escalating unresolved definition or rule conflicts. Subject-matter experts can contribute knowledge, but they should not become de facto owners just because they perform ad hoc cleanup. Technical custodians may implement changes, and a cleansing project may remove current defects, but neither establishes ongoing accountability for preventing recurrence.

• Volunteer cleanup leaves accountability informal and depends on goodwill rather than governed responsibilities.
• Technical ownership confuses custody of systems with business accountability for customer segment meaning and quality.
• One-time cleansing treats symptoms but does not create ongoing stewardship for rules, monitoring, and escalation.

Question 3

Topic: Roles Responsibilities and Decision Rights

A bank has appointed data owners for each major domain, but customer, account, and product teams still use different business definitions and escalate quality issues inconsistently. The data governance council has approved policies, but adoption is uneven across business units. Which action best demonstrates the role of a stewardship network in this situation?

Options:

• A. Coordinate stewards across domains to align definitions, rules, issues, and messages

• B. Let each project team define terms for its own delivery scope

• C. Have the council personally resolve each disputed data definition

• D. Assign database administrators to correct all quality defects

Best answer: A

Explanation: A stewardship network is the community mechanism that helps governance operate across domains. Data owners retain accountability and a council may set policy or make major decisions, but stewards coordinate day-to-day adoption: clarifying business definitions, proposing or applying quality rules, routing issues, sharing decisions, and communicating standards to their areas. In the bank scenario, the problem is not only a missing policy or a technical defect. It is inconsistent adoption across customer, account, and product domains. A cross-domain steward community is suited to harmonize practices and surface unresolved conflicts for escalation when needed.

The key distinction is that the stewardship network enables consistent business practice across domains; it does not replace ownership, council authority, or technical custody.

• Council handles everything is too centralized; councils decide and escalate major matters but should not personally resolve every working-level definition dispute.
• DBA cleanup treats quality issues as only technical defects and misses business ownership of rules and definitions.
• Project-only definitions increases inconsistency because project scope does not provide enterprise or cross-domain alignment.

Question 4

Topic: Roles Responsibilities and Decision Rights

A finance organization has named data stewards for customer and product domains, but project teams continue to ignore steward recommendations. The stewards can document issues, yet no one has authorized them to approve definitions, require remediation, or escalate unresolved conflicts. What is the best governance action?

Options:

• A. Define steward decision rights and escalation authority

• B. Assign more technical data custodians

• C. Schedule additional glossary training sessions

• D. Create a larger data issue backlog

Best answer: A

Explanation: Named stewards are not effective unless the operating model gives them clear responsibilities, decision rights, and an escalation route. In this situation, the gap is not awareness or documentation; it is authority. The governance council or accountable data owners should approve a stewardship charter, RACI, or similar artifact that states which decisions stewards can make, which decisions require owner approval, and how unresolved conflicts move to a governance forum. That turns stewardship from informal advice into governed accountability.

Adding custodians, more backlog records, or more training may support the program, but none solves the missing empowerment problem.

• More custodians confuses technical custody with business stewardship authority.
• Larger backlog records more issues but does not create the power to resolve or escalate them.
• More training may improve awareness, but the stated failure is lack of authority, not lack of knowledge.

Question 5

Topic: Roles Responsibilities and Decision Rights

A bank’s customer master data is managed in a CRM platform by the IT operations team. Business units disagree on the definition of “active customer,” a privacy audit found inconsistent approval of customer attribute access, and data quality fixes are being prioritized by system administrators based on ticket volume. The governance council must reduce risk without moving technical system administration out of IT. Which governance decision is best?

Options:

• A. Assign the CRM vendor to approve access requests

• B. Make IT operations the customer data owner

• C. Name business data owners for customer data decisions

• D. Let each project define customer terms independently

Best answer: C

Explanation: Confusing business ownership with technical custody creates a governance risk: technical teams may make business decisions about meaning, acceptable quality, access justification, and risk tolerance without the accountability to own business outcomes or compliance impact. In DAMA-aligned governance, data owners are accountable for business decisions about data, while custodians administer and protect systems according to approved policies, standards, and controls. Here, IT should continue operating the CRM platform, but the governance council should establish named business owners for customer data and define their decision rights with stewardship support and escalation paths. The key takeaway is that system control is not the same as business accountability for data.

• IT as owner fails because system administration does not provide business accountability for definitions, access intent, or accepted risk.
• Project-level definitions fail because independent meanings would worsen cross-domain inconsistency and undermine shared customer data.
• Vendor access approval fails because an external system provider should not decide business authorization or privacy risk acceptance.

Question 6

Topic: Roles Responsibilities and Decision Rights

A company is standardizing customer reporting across regions. Sales wants each region to keep its local definition of active customer because compensation dashboards are already built around it. Compliance needs one defensible definition for regulated retention reporting within 60 days. No single business owner is accountable today, and the governance charter says cross-domain definition conflicts with regulatory impact must be escalated through the stewardship group to the Data Governance Council. What is the best governance decision?

Options:

• A. Ask IT to select the definition used by the customer data warehouse

• B. Let the highest-revenue region define active customer for all reports

• C. Have stewards document impacts and escalate a recommended enterprise definition to the council

• D. Keep separate glossary definitions until a master data tool is implemented

Best answer: C

Explanation: Conflict resolution in data governance should use agreed decision rights, especially when local practices affect enterprise reporting or compliance. Here, regional preferences have business value, but the regulatory reporting need and ownership gap make this more than a local reporting issue. The stewardship group should prepare the evidence: current definitions, business impacts, risks, and recommended standard or controlled exceptions. The Data Governance Council is the right forum to approve the enterprise definition, assign accountability, and ensure affected processes align. Technical teams may implement the decision, but they should not own the business meaning. The key takeaway is that governance resolves definition conflicts by applying decision rights and escalation paths, not by defaulting to the loudest region or the current system design.

• Letting the highest-revenue region decide ignores the regulatory impact and creates a weak precedent for enterprise definitions.
• Asking IT to choose confuses technical custody with business accountability for data meaning.
• Waiting for a master data tool delays a governance decision that is needed within 60 days and does not solve ownership.

Question 7

Topic: Roles Responsibilities and Decision Rights

A bank is standardizing the definition of “active customer” for regulatory reporting and marketing analytics. Compliance owns the reporting obligation, Marketing and Retail Banking are major users, Data Management will implement glossary and quality-rule updates, and the current stewardship group can facilitate but has no authority to resolve cross-domain conflicts. Which governance decision best assigns accountability while preserving appropriate participation?

Options:

• A. Name Compliance as accountable decision owner, with Marketing and Retail Banking consulted

• B. Make the stewardship group accountable because it coordinates the definition work

• C. Assign Data Management accountability because it updates metadata and rules

• D. Notify Compliance after Marketing and Retail Banking agree on the definition

Best answer: A

Explanation: Decision accountability belongs with the role or body that has the authority and obligation to make the decision, not necessarily the group doing the work. In this situation, the definition affects regulatory reporting, so Compliance should be accountable for the final decision. Marketing and Retail Banking are important participants because they use the term and can identify business impacts. Data Management implements the approved glossary and quality-rule changes, and stewards may coordinate the workflow or escalate conflict. Accountability should be singular and clear, while participation can include consultation, implementation, and notification responsibilities.

• Coordination is not authority because a stewardship group that facilitates work cannot be accountable for resolving a cross-domain decision without delegated authority.
• Implementation is not ownership because updating metadata and rules is execution, not accountability for the business definition.
• Notification is too weak because Compliance must decide or approve a regulatory definition, not merely be informed after other domains agree.

Question 8

Topic: Roles Responsibilities and Decision Rights

A customer master record is shared by Sales, Support, and Billing. Sales wants to change the definition of “active customer,” Support objects because service metrics will change, and IT says it can implement either definition. The current stewardship group is advisory only, and a privacy audit requires clear accountability for changes to customer-status rules. Which governance decision best clarifies the approval role?

Options:

• A. Let IT approve the definition because it controls the customer master platform

• B. Require all domain stewards to unanimously approve every status-rule change

• C. Have the data governance council designate an accountable business data owner for customer status changes

• D. Let the project manager approve the definition for the current release

Best answer: C

Explanation: Shared data changes need explicit decision rights, especially when definitions affect multiple business domains and auditability. DAMA-aligned governance separates accountability for data decisions from technical custody. A data owner has business accountability for approving policies, definitions, and rules for a data domain or subject area. Data stewards provide subject-matter input, assess impacts, and help manage issues, but an advisory stewardship group does not automatically hold final approval authority. IT custodians manage platforms and implement approved changes; they should not own the business meaning of customer status. The governance council can resolve the ownership gap by assigning or confirming the accountable owner and escalation path.

• Technical control fails because platform custody does not create authority over business definitions.
• Release urgency fails because project delivery authority is temporary and does not resolve ongoing shared-data accountability.
• Unanimous stewardship fails because stewards advise and coordinate; requiring unanimity can block governance without clarifying ownership.

Question 9

Topic: Roles Responsibilities and Decision Rights

A bank’s customer data domain has recurring delays because both the data governance council and three product committees approve the same customer attribute changes. Urgent changes are sometimes made by project teams before approval to meet release dates. The data owner is named, but stewardship responsibilities are inconsistent across regions. Which governance decision best addresses the duplicated approvals and informal overrides?

Options:

• A. Let project teams approve urgent changes and notify stewards afterward

• B. Define a decision-rights matrix with delegated steward decisions and escalation criteria

• C. Require all customer attribute changes to be approved only by the council

• D. Create a new regional review board for each product committee

Best answer: B

Explanation: Decision-rights design clarifies who can decide, who must be consulted, and when a matter must be escalated. In this scenario, the main problems are overlapping approvals, bottlenecks, and informal project overrides. A decision-rights matrix can assign routine customer attribute changes to accountable stewards or the data owner, require consultation from affected product or regional groups, and reserve council review for cross-domain, high-risk, or policy-impacting changes. That preserves governance authority without turning every operational decision into a council agenda item. It also makes urgent changes follow an agreed exception or escalation path rather than bypassing governance.

• Council-only approval removes duplication but creates a larger bottleneck and does not use stewardship capacity.
• Project-team approval formalizes the informal override problem and weakens data ownership accountability.
• Additional regional boards add another approval layer and are likely to increase duplication rather than clarify authority.

Question 10

Topic: Roles Responsibilities and Decision Rights

A bank is creating an enterprise glossary entry for active customer. Sales and Compliance stewards disagree on whether dormant accounts should be included. The governance charter names a Customer data owner accountable for business meaning and data quality priorities for the Customer domain. Who is best positioned to approve the final definition?

Options:

• A. Sales data steward

• B. Customer data owner

• C. Data custodian

• D. Metadata tool administrator

Best answer: B

Explanation: Data ownership carries accountability for the business meaning, acceptable use, and priority of data within a domain. Stewards often draft definitions, collect stakeholder input, document rules, and manage issues, but they do not normally overrule domain accountability when a business meaning conflict must be resolved. Custodians and tool administrators support the technical environment, access mechanisms, and metadata tooling; they can implement the approved definition but should not decide its business meaning. The key distinction is decision authority versus support or execution responsibility.

• Sales stewardship is relevant input, but a single departmental steward should not settle an enterprise definition conflict alone.
• Technical custody supports storage, access, and platform controls, not business approval of glossary meaning.
• Tool administration can publish or configure the glossary entry, but it does not grant business decision rights.

Continue in the web app

Use IT Mastery for interactive DAMA CDMP Data Governance Specialist practice with mixed sets, timed mocks, topic drills, explanations, and progress tracking.

Try DAMA CDMP Data Governance Specialist on Web

Related focused pages

• Free DAMA CDMP Data Governance Specialist Full-Length Practice Exam
• Data Governance Foundations and Principles
• Governance Strategy Business Case and Value
• Governance Operating Model and Organization
• Policies Standards Rules and Controls
• Governance Issue Management and Resolution
• Glossary and Metadata Governance
• Data Quality Governance
• Security and Compliance Alignment
• Master Reference and Architecture Governance
• Governance Metrics Maturity and Improvement
• Governance Program Operations