Free DAMA CDMP Governance Practice Questions: Glossary and Metadata Governance

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: Business Glossary Metadata and Definition Governance

A bank’s risk team challenges a quarterly “active customer” exposure metric. The metadata catalog shows technical lineage from CRM to the risk warehouse, but the business glossary entry for Active Customer has no approved owner, no agreed definition, and no links to the quality rules or control reports used for regulatory reporting. Which governance response best fits the issue?

Options:

• A. Have the data owner and stewards approve the glossary term and link it to lineage, rules, and controls

• B. Approve separate definitions for each reporting team

• C. Move the metric calculation into a new reporting tool

• D. Ask the data custodian to refresh the lineage scan

Best answer: A

Explanation: Metadata governance connects business definitions, ownership, lineage, quality rules, and controls so stakeholders can understand and trust reported data. In this case, the technical lineage exists, but the governed business meaning is missing. The appropriate response is not just a catalog refresh or a tool change; it is a stewardship and ownership action to approve the glossary definition and bind it to the relevant data flows, quality rules, and reporting controls. That creates traceability from the regulatory metric back to an agreed business term and accountable decision record. Technical custody supports the process, but business ownership resolves the definition and trust problem.

• Lineage-only fix fails because the scan may show movement of data, but it does not approve business meaning or control linkage.
• Separate definitions weakens trust because regulatory reporting needs an agreed meaning or clearly governed exceptions.
• Tool replacement misses the governance issue because the current gap is accountability and approved metadata, not calculation software.

Question 2

Topic: Business Glossary Metadata and Definition Governance

A data governance team is reviewing a conflict between two executive dashboards. Both dashboards use the same customer source table, the same reporting date, and validated row counts after extraction. The aggregation logic and visual filters have also been checked. Sales defines an “active customer” as any customer with a quote in the last 12 months, while Finance defines it as any customer with a paid invoice in the last 12 months. What is the most likely cause of the conflict?

Options:

• A. Incorrect extraction from the source table

• B. Misleading visualization filter configuration

• C. Faulty aggregation in the dashboard calculation

• D. Inconsistent business meaning for the metric

Best answer: D

Explanation: A semantic inconsistency occurs when stakeholders use the same term or metric label but attach different business meanings to it. Here, the technical checks reduce the likelihood of extraction, calculation, or visualization problems: both dashboards use the same source, date, row counts, aggregation logic, and filters. The decisive difference is that Sales and Finance define “active customer” using different business events: quote activity versus paid-invoice activity. This is a definition governance issue that should be resolved through business glossary ownership, approved definitions, and stewardship escalation when needed. The key signal is not that the numbers differ, but that the same metric name represents different business concepts.

• Extraction defect does not fit because the source table, reporting date, and extracted row counts have already been validated.
• Aggregation fault does not fit because the calculation logic was checked and no arithmetic or grouping error is indicated.
• Visualization filter issue does not fit because the filters were reviewed and the difference remains tied to business definition.

Question 3

Topic: Business Glossary Metadata and Definition Governance

Marketing and Finance each use “active customer” for different but valid business purposes. Board dashboards currently mix the two counts, creating inconsistent enterprise reporting. The data governance council owns enterprise KPI definitions, domain stewards are available, and the business glossary lacks usage context and lineage links. Which governance decision is BEST?

Options:

• A. Let BI developers rename fields inside dashboard code

• B. Keep both definitions informal until the glossary is redesigned

• C. Govern both definitions with context and an enterprise KPI mapping

• D. Require all domains to adopt Finance’s audited definition

Best answer: C

Explanation: When two definitions are both valid, semantic governance should not force a false single meaning. The better action is to govern the meanings explicitly: record each context-specific glossary definition, assign accountable owners and stewards, document usage rules, and link the terms to reports, lineage, and the enterprise KPI definition approved by the governance council. This allows Marketing and Finance to keep fit-for-purpose definitions while preventing mixed use in board reporting. The key is controlled coexistence: distinct names or qualifiers, approved mappings, and clear report-level guidance.

• Single imposed meaning fails because Finance’s audited need does not invalidate Marketing’s legitimate business definition.
• BI-only renaming fails because technical changes do not establish business decision rights, stewardship, or governed semantic standards.
• Informal notes fail because the current reporting confusion needs active governance, not a delayed glossary cleanup.

Question 4

Topic: Business Glossary Metadata and Definition Governance

A retailer has two business-approved definitions of active customer. Marketing counts anyone who opened or clicked a campaign in the last 90 days. Finance counts anyone with a settled purchase in the last 12 months. Both definitions are valid for their processes, but executives are confused when enterprise dashboards use the same label with different numbers. What is the best governance action?

Options:

• A. Ask BI developers to rename fields independently

• B. Govern both glossary terms with context and usage rules

• C. Store both calculations as technical metadata only

• D. Select Finance’s definition as the only enterprise meaning

Best answer: B

Explanation: Semantic governance does not always require forcing one universal definition. When two definitions are legitimately valid for different business purposes, the glossary should make that distinction explicit. Each term should have an approved definition, business owner or steward, usage context, calculation rule, and guidance for report labels or metric selection. Enterprise reporting can then distinguish concepts such as marketing active customer and financial active customer, or apply a governed enterprise metric where a single cross-domain view is required.

The key is to manage meaning as a governed business asset, not as an isolated dashboard naming problem. Clear semantic context lets both definitions coexist while reducing reporting confusion.

• Single-definition forcing fails because one valid business meaning would be suppressed without resolving the underlying semantic difference.
• Independent BI renaming fails because local report changes do not establish governed ownership, approval, or consistent enterprise usage.
• Technical-only metadata fails because the conflict is about business meaning and reporting interpretation, not only field storage or lineage.

Question 5

Topic: Business Glossary Metadata and Definition Governance

A finance division deploys a metadata catalog that automatically scans databases and BI reports. After three months, users still dispute the definition of “active customer,” and no one is accountable for approving lineage changes shown in the catalog. Which action best demonstrates metadata governance rather than tool installation or automated capture alone?

Options:

• A. Add more technical metadata fields to the catalog

• B. Assign stewards and approval workflows for glossary and lineage changes

• C. Increase scanner frequency for all database connections

• D. Require every report owner to install the catalog browser

Best answer: B

Explanation: Metadata governance is the oversight of metadata as a managed business asset. Automated capture can populate a catalog with table names, report dependencies, and lineage signals, but it does not resolve who may define a business term, approve a lineage interpretation, or handle conflicting definitions. In this scenario, the missing capability is accountability: named stewards, decision rights, review workflows, and escalation for glossary and lineage changes. The tool can support the process, but governance determines ownership, rules, and accepted meaning.

• Scanner frequency may improve freshness, but it does not settle definition conflicts or approval authority.
• More metadata fields may enrich the catalog, but added content without ownership can increase confusion.
• Catalog browser adoption improves access to metadata, but viewing metadata is not the same as governing it.

Question 6

Topic: Business Glossary Metadata and Definition Governance

A bank’s metadata catalog scans databases nightly and extracts table names, column names, data types, and lineage. Two business units still use different meanings for active customer in the same regulatory report. Which activity best represents business glossary governance for this term?

Options:

• A. Approve a governed business definition with named owner and stewards

• B. Add the source column data types to the data dictionary

• C. Extract lineage from ETL jobs into the catalog

• D. Increase the catalog scan frequency for reporting databases

Best answer: A

Explanation: Business glossary governance controls the meaning, accountability, and approval of business terms such as active customer. The decisive issue is not whether the catalog can find columns or lineage; it is whether the organization has agreed on a governed definition and assigned decision rights to the appropriate business owner and stewards. Data dictionaries, catalog scans, and technical metadata extraction support discovery and documentation, but they do not by themselves resolve conflicting business definitions. The governance activity should produce an approved term, ownership, stewardship responsibilities, and a repeatable approval path for future changes.

• More scanning may improve metadata freshness, but it does not settle the business meaning of the term.
• Data dictionary updates document technical structures, but column types do not establish enterprise business definitions.
• Lineage extraction shows data movement and transformation, but it does not assign ownership or approve terminology.

Question 7

Topic: Business Glossary Metadata and Definition Governance

A company is standardizing its business glossary after finding three different definitions of “active customer” in sales dashboards, regulatory reporting, and churn analysis. The Customer data owner is accountable for the term, data stewards maintain glossary content, and the governance council resolves cross-domain disputes. Which approval workflow best keeps the definition authoritative, current, and tied to measurable business use?

Options:

• A. Steward drafts, impacted metric owners review, data owner approves, council escalates disputes

• B. Governance council directly approves every glossary wording change in quarterly meetings

• C. Requesting project team approves the definition for its dashboard and notifies stewards

• D. Catalog administrator approves edits after checking naming and formatting standards

Best answer: A

Explanation: Authoritative glossary definitions need business accountability, not only metadata administration. A steward can coordinate drafting and maintenance, but the accountable data owner should approve the business meaning. Impacted metric or report owners should review whether the definition supports measurable use, such as sales dashboards, regulatory reporting, or churn analysis. The governance council should handle unresolved cross-domain conflicts, not become the routine editor for every term. This balance keeps the glossary trusted, usable, and current while preserving clear decision rights.

• Administrator approval checks metadata hygiene, but it does not establish business authority for the meaning of the term.
• Project approval creates local definitions and risks another conflict across dashboards, reports, and analysis.
• Council approval for every edit may preserve authority, but it creates a bottleneck and misuses the escalation forum for routine stewardship work.

Question 8

Topic: Business Glossary Metadata and Definition Governance

A bank is preparing a regulated risk report. Finance and Risk use different definitions for the same exposure metric, lineage from source systems to the report is incomplete, and prior audit findings require evidence of who approved definition and rule changes. Data stewards exist in each domain, but decision rights are unclear. Which metadata governance action is the BEST decision?

Options:

• A. Run one-time profiling on the report tables before submission

• B. Create governed glossary and lineage ownership for critical data elements

• C. Let each domain maintain separate definitions in its local catalog

• D. Have the BI team rename report fields to match user expectations

Best answer: B

Explanation: Metadata governance should establish accountable business ownership for critical data elements, not just document technical fields. In this case, the bank needs governed definitions, approved decision rights, lineage from source to report, quality rules tied to the agreed terms, and auditable change evidence. A business glossary connected to lineage and stewardship workflows supports discovery because users can find approved meanings, impact analysis because changes can be traced through data flows, auditability because approvals are recorded, and trusted reporting because quality rules align to common definitions. Technical cataloging and profiling can support the process, but they do not resolve unclear authority or conflicting business meaning by themselves.

• Report renaming improves labels but does not establish approved definitions, lineage, quality-rule ownership, or audit evidence.
• One-time profiling may identify defects, but it does not govern ongoing metadata decisions or change approvals.
• Separate local definitions preserve the cross-domain conflict and weaken trust in regulated reporting.

Question 9

Topic: Business Glossary Metadata and Definition Governance

Two business units use the term “active customer” in executive reporting. Retail includes any customer with a purchase in the last 12 months, while Support includes any customer with an open service contract. Both definitions are legitimate in their own contexts, but the CEO dashboard currently shows a single unlabeled “active customer” metric. What governance action best resolves the conflict?

Options:

• A. Let each report owner define the term locally

• B. Ask the data warehouse team to choose one definition

• C. Merge both populations into one enterprise metric

• D. Create governed glossary entries with context and approved metric names

Best answer: D

Explanation: Conflicting business terms are a semantic governance issue when multiple meanings are valid in different contexts. The appropriate response is to govern the meaning: document approved glossary entries, assign business ownership, specify context, and ensure reports use clear metric names such as “active purchasing customer” and “active contract customer.” This avoids forcing a false single definition while preventing ambiguity in enterprise reporting. Technical teams may implement the change, but they should not decide the business meaning. The key distinction is between resolving semantic ambiguity through governed definitions and simply changing data processing or report design.

• Technical custody fails because warehouse teams can implement definitions, but business owners and stewards should govern metric meaning.
• Forced merger fails because the scenario says both meanings are legitimate in different business contexts.
• Local definitions fail because unmanaged report-specific meanings recreate ambiguity in executive reporting.

Question 10

Topic: Business Glossary Metadata and Definition Governance

A governance analyst is reviewing a draft business glossary entry before it is published.

Which missing information is the most important gap for glossary ownership and approval?

Options:

• A. Database administrator for CRM

• B. ETL developer for campaign feeds

• C. Accountable business data owner

• D. Glossary tool administrator

Best answer: C

Explanation: A governed business glossary entry needs more than a clear definition and a named steward. The steward may coordinate drafting, review, and issue handling, but approval of a business term should be tied to an accountable business owner or owning role with decision rights. In this entry, the definition, context, related terms, steward, custodian, and approval status are visible. The gap is the missing accountable approver who can accept responsibility for the term’s meaning and future changes. Technical roles may support systems, metadata, or data movement, but they do not normally own the business meaning of glossary terms.

• Technical custody fails because CRM operations may manage the platform, not approve the business meaning of a glossary term.
• Tool administration fails because maintaining glossary software is not the same as owning term decisions.
• ETL development fails because building campaign feeds does not establish authority over glossary definitions.

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
• Roles Responsibilities and Decision Rights
• Policies Standards Rules and Controls
• Governance Issue Management and Resolution
• Data Quality Governance
• Security and Compliance Alignment
• Master Reference and Architecture Governance
• Governance Metrics Maturity and Improvement
• Governance Program Operations