Free DAMA CDMP Fundamentals Practice Questions: Metadata Management

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: Metadata Management

A global retailer has separate metadata stores in its BI platform, data catalog, ETL tool, and data governance workflow. Business users cannot find trusted data assets, glossary terms differ by region, lineage is incomplete, and teams repeatedly recreate similar definitions. Which metadata architecture choice best addresses these needs across tools and business domains?

Options:

• A. Spreadsheet glossary maintained by business analysts

• B. Separate repositories owned by each tool team

• C. Physical database catalog for production schemas only

• D. Integrated metadata repository with shared standards

Best answer: D

Explanation: Metadata architecture should enable metadata to be captured, connected, governed, and reused across the data environment. In this scenario, the main problems are fragmented repositories, inconsistent business terms, incomplete lineage, and duplicated definition work. An integrated metadata repository, supported by common standards and connections to tools such as BI, ETL, catalogs, and governance workflows, creates a shared view of business, technical, operational, and lineage metadata. It improves discoverability because users can search across domains, consistency because definitions follow shared standards, traceability because lineage can connect sources to reports, and reuse because approved terms and asset descriptions are visible. Tool-specific stores may still exist, but they need integration and governance rather than isolation.

• Tool isolation preserves local control but keeps metadata fragmented and weakens cross-domain traceability.
• Spreadsheet glossary may help document some terms but does not scale well for lineage, integration, or reuse across systems.
• Schema-only cataloging captures technical metadata but misses business definitions, stewardship context, and broader lineage.

Question 2

Topic: Metadata Management

A data steward is reviewing a proposed change to the Customer_Status field in a source CRM system. Before approving the change, the governance control requires evidence of which downstream reports, interfaces, and data stores could be affected. Which metadata evidence best supports that control activity?

Options:

• A. Data classification label for Customer_Status

• B. End-to-end data lineage for Customer_Status

• C. Business glossary definition for Customer_Status

• D. Current data quality score for Customer_Status

Best answer: B

Explanation: Impact analysis depends on lineage metadata. Lineage records where a data element originates, how it is transformed, where it is stored, and which outputs consume it. For a proposed source-field change, that evidence helps governance and stewardship teams identify affected reports, interfaces, data stores, and controls before approval. A glossary definition is useful for semantic clarity, a quality score is useful for fitness assessment, and a classification label is useful for security or privacy handling. None of those directly traces downstream dependency.

• Glossary definition helps align business meaning, but it does not show dependent systems or reports.
• Quality score indicates whether data meets expectations, not what will break if the field changes.
• Classification label supports protection requirements, but it is not evidence for downstream impact analysis.

Question 3

Topic: Metadata Management

A bank finds that its ETL tool, BI platform, data quality tool, and access-control system each show different lineage, business definitions, classifications, and ownership for the same customer data elements. Users cannot tell which metadata to trust. What is the best architecture response?

Options:

• A. Move the metadata into the BI semantic layer only.

• B. Publish a spreadsheet cross-reference between the tool repositories.

• C. Use an integrated metadata repository with authoritative sources by metadata type.

• D. Appoint one data owner to approve every metadata update manually.

Best answer: C

Explanation: Metadata architecture should define how metadata is captured, stored, integrated, synchronized, and governed across repositories and tools. When multiple platforms hold conflicting lineage, definitions, classifications, and ownership, the response is not simply to choose one operational tool or add manual reconciliation. A better architecture establishes an integrated metadata repository or catalog, a common metadata model where needed, harvesting or exchange mechanisms, and clear authoritative sources for each metadata type. Governance roles still matter, but they operate through the architecture rather than replacing it. The key is to make metadata trustworthy and reusable across the data environment, not trapped in inconsistent tool-specific silos.

• Manual approval bottleneck does not integrate repositories or resolve how metadata is synchronized across tools.
• BI-only storage addresses reporting definitions but misses operational lineage, classifications, and ownership outside analytics.
• Spreadsheet cross-reference may document differences temporarily, but it is not a sustainable metadata repository integration approach.

Question 4

Topic: Metadata Management

A regional bank has launched an enterprise data catalog, but business users still rely on spreadsheets because many catalog entries have missing business definitions, different names for the same customer attributes, and no visible owner for updates. The data governance council has limited capacity and wants to improve trusted reporting before expanding the catalog to new domains. What is the best professional decision?

Options:

• A. Delay catalog use until every data asset is fully documented

• B. Assign domain stewards to curate priority metadata and approve standards

• C. Load all database schemas into the catalog automatically

• D. Ask report developers to define terms within each dashboard

Best answer: B

Explanation: Metadata governance and stewardship make metadata trustworthy and usable by assigning accountability, standards, and ongoing maintenance. In this situation, the main problems are missing definitions, inconsistent naming, and no visible owner for updates. A practical governance response is to focus steward effort on priority domains that support trusted reporting, agree on common definitions and naming standards, and establish approval and update responsibilities. This improves metadata quality and encourages adoption without requiring the whole enterprise catalog to be perfect at once.

A broad technical import may increase catalog volume, but it does not resolve business meaning, ownership, or consistency. The key takeaway is that useful metadata needs accountable stewardship, not just automated inventory.

• Schema loading only adds technical metadata but leaves business definitions, standards, and ownership unresolved.
• Dashboard-level definitions can create more inconsistency because each report team may define shared terms differently.
• Waiting for perfection delays adoption and ignores the council’s need to improve priority reporting first.

Question 5

Topic: Metadata Management

A data catalog team is improving a customer profitability data set used by finance analysts. The analysts can find the table, but they disagree about how to interpret the fields and measures in reports. Which metadata would best address the analysts’ immediate need for business interpretation?

Options:

• A. Access logs, change history, and retention evidence

• B. Job run times, load status, and processing duration

• C. Database indexes, partitions, and storage locations

• D. Business definitions, metric meanings, and approved usage notes

Best answer: D

Explanation: Metadata for business interpretation helps people understand the meaning, context, and appropriate use of data. For a finance audience, that includes business glossary definitions, metric definitions, valid calculation meaning, ownership or stewardship context, and usage guidance. These elements reduce inconsistent interpretation of fields and measures across reports. Technical metadata supports operation of systems, such as schemas, storage structures, jobs, and interfaces. Audit or operational evidence supports traceability, compliance, and control monitoring, such as logs, lineage evidence, and retention records. The need described is not to run the pipeline or prove control activity; it is to make the data understandable for business decision making.

• Operational status helps monitor processing reliability, but it does not define what finance measures mean.
• Physical structures help technical teams manage performance and storage, not business interpretation.
• Audit evidence supports accountability and compliance, but it does not resolve disagreement about field and measure meaning.

Question 6

Topic: Metadata Management

A financial services firm has multiple analytics teams rebuilding similar regulatory reports. Each team repeatedly spends weeks rediscovering source systems, business definitions, data owners, and transformation rules. The firm has named data stewards but no shared repository for their knowledge, and leadership wants faster reuse without funding a warehouse migration. What is the best professional decision?

Options:

• A. Assign database administrators as the sole contacts for all source data questions

• B. Establish an enterprise metadata catalog with glossary, lineage, ownership, and transformation metadata

• C. Create a new centralized data warehouse for all regulatory reporting data

• D. Ask each analytics team to document its own report assumptions locally

Best answer: B

Explanation: Metadata management supports reuse by capturing and publishing knowledge about data assets: where data comes from, what it means, who is accountable for it, and how it is transformed. In this situation, the main problem is not the absence of a new reporting platform; it is repeated rediscovery across teams. A metadata catalog linked to a business glossary, lineage, stewardship ownership, and transformation rules gives analysts a governed place to find and trust reusable knowledge. Named stewards can curate and approve the content, while teams can reduce duplicate discovery work. The key takeaway is that metadata-enabled reuse should make existing data knowledge visible and governed before funding major platform changes.

• Warehouse-first thinking misses the stated funding constraint and may not solve missing definitions, ownership, or lineage by itself.
• Local documentation preserves team silos, so future teams still must rediscover or reconcile inconsistent assumptions.
• DBA-only ownership confuses technical custody with business accountability for definitions, stewardship, and data use rules.

Question 7

Topic: Metadata Management

A retailer is improving reuse of customer data across analytics, integrations, data quality monitoring, and privacy controls. The data office wants an artifact that helps teams understand what a data element means, where it comes from, who is accountable, how it is transformed, which quality rules apply, and whether access must be restricted. Which artifact best fits this need?

Options:

• A. A metadata catalog entry for the data element

• B. A master customer record

• C. A customer status code set

• D. A dashboard layout specification

Best answer: A

Explanation: Metadata describes data assets so they can be governed, understood, trusted, protected, and reused. For a data element, metadata may include business definitions, stewardship ownership, lineage, source-to-target mappings, data quality rules, security classification, and warehouse usage. These details support governance decisions, architecture traceability, modelling consistency, integration design, quality monitoring, security controls, warehousing, and master data management. The key distinction is that metadata is information about the data, not the customer record, code values, or report presentation itself.

• Master record confusion fails because a master customer record is governed data, not the descriptive information that explains and controls its use.
• Reference data confusion fails because a status code set standardizes allowed values but does not capture lineage, ownership, quality rules, and classification for a data element.
• Presentation focus fails because a dashboard layout specification addresses report display, not enterprise metadata needed across data management activities.

Question 8

Topic: Metadata Management

A bank is preparing a regulatory reporting review. Business terms are maintained in a spreadsheet, ETL lineage is documented in a separate tool, and data quality rules are stored in a ticketing system. The term “active customer” has different definitions in the spreadsheet and in report documentation. What is the most significant metadata risk in this environment?

Options:

• A. Inconsistent report interpretation and weak traceability

• B. Excess storage consumption from duplicate metadata

• C. Loss of transactional data from source systems

• D. Slow database query performance during reporting

Best answer: A

Explanation: Metadata architecture should support connected, authoritative, and accessible metadata across business, technical, and operational contexts. When business definitions, lineage, and data quality rules are split across repositories without integration or stewardship control, users may apply different meanings to the same term and struggle to trace data from source to report. In the bank’s review, the conflicting definition of “active customer” directly threatens regulatory confidence because the organization cannot easily demonstrate consistent meaning, lineage, and control over reported data.

Storage overhead is secondary; the core issue is trust and interpretability of data assets.

• Storage overhead may occur, but duplicate metadata is not the main risk when definitions conflict in regulated reporting.
• Query performance depends on database design and workload, not primarily on fragmented metadata repositories.
• Source data loss is an operational storage or processing failure, not the direct result of disconnected metadata documentation.

Question 9

Topic: Metadata Management

A regional bank has purchased a metadata catalog that can automatically scan databases and BI reports. Business teams still disagree on definitions for key metrics, several critical data elements lack accountable stewards, and audit needs evidence that lineage and classifications are reviewed, not just collected. What is the best professional decision?

Options:

• A. Delay metadata work until all source systems are standardized

• B. Let each project team define metadata locally

• C. Establish metadata governance and stewardship practices around the catalog

• D. Run more frequent automated scans across all platforms

Best answer: C

Explanation: Metadata management includes governance, stewardship, standards, roles, quality controls, and lifecycle processes for metadata. Automated scanning can populate technical metadata such as tables, columns, jobs, and report dependencies, but it cannot by itself resolve business definition conflicts, assign accountability, approve classifications, or provide reliable audit evidence. In this situation, the catalog is useful infrastructure, but the bank’s risk is unmanaged metadata: disputed metric definitions, missing stewardship, and unreviewed lineage and classification information. The practical decision is to place governance and stewardship around the tool so scanned metadata becomes trusted, maintained, and usable for business and compliance purposes.

• More scanning increases inventory coverage but does not resolve definitions, accountability, or review evidence.
• Local project definitions would worsen inconsistency because shared metrics need common standards and stewardship.
• Waiting for standardization delays risk reduction; metadata governance can begin while systems remain diverse.

Question 10

Topic: Metadata Management

A data steward is reviewing a planned change in the CRM system: Customer.email will change from “primary contact email” to “login email.” The team needs to identify which downstream reports, extracts, and data quality rules could be affected before release.

Which action best fits the need?

Options:

• A. Wait for data quality failures after deployment

• B. Ask report developers to check their own dashboards

• C. Perform lineage-based impact analysis across the mapped flow

• D. Update only the CRM data dictionary entry

Best answer: C

Explanation: Lineage reasoning connects a source data element to downstream transformations, stores, rules, reports, and consumers. Because the CRM field’s business meaning is changing, the impact is not limited to a physical column or one application. The steward should trace the mapped flow through MDM, the warehouse, the dashboard, the compliance extract, and any quality or matching rules that depend on the original meaning. This supports early notification, rule review, glossary updates, and controlled change management before consumers receive misleading data. A local dictionary update records the change, but it does not identify downstream business impact.

• Local documentation only misses dependent MDM, warehouse, BI, compliance, and quality-rule uses.
• Informal developer checking may miss non-report consumers such as extracts, matching rules, and governed definitions.
• Post-release detection is reactive and allows avoidable reporting or compliance issues to reach consumers.

Continue in the web app

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

Try DAMA CDMP Data Management Fundamentals on Web

Related focused pages

• Free DAMA CDMP Data Management Fundamentals Full-Length Practice Exam
• Data Management Process
• Big Data
• Data Architecture
• Document and Content Management
• Data Ethics
• Data Governance
• Data Integration and Interoperability
• Master and Reference Data Management
• Data Modelling and Design
• Data Quality
• Data Security
• Data Storage and Operations
• Data Warehousing and Business Intelligence