Free DAMA CDMP Governance Practice Questions: Master Reference and Architecture 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: Master Reference and Architecture Governance

A company’s customer master hub receives customer status from CRM and billing. CRM marks a customer as Inactive when no open sales opportunity exists, while billing marks the same customer as Active when there is an open invoice. The status drives collections, marketing suppression, and regulatory notices. Which decision right is most important for a durable resolution?

Options:

• A. Technical authority to select the feed with the cleanest nightly load

• B. Steward authority to document both meanings in the glossary

• C. Application-owner authority to preserve local meanings independently

• D. Business authority to approve the enterprise status meaning and precedence rules

Best answer: D

Explanation: Master and reference data conflicts are not solved durably by choosing a convenient system feed or recording disagreement. When a shared value affects multiple business outcomes, governance must assign decision rights to an accountable business owner or governance forum. That authority should approve the enterprise meaning, valid values, source precedence or survivorship rules, and exception handling. Data stewards can prepare analysis and maintain glossary or mapping artifacts, and custodians can implement the approved rules, but neither substitutes for accountable business ownership of the shared data decision. The key distinction is authority over meaning and business use, not technical custody of the data movement.

• Cleanest feed confuses data quality or integration convenience with authority to define enterprise meaning.
• Glossary documentation is useful stewardship work, but it leaves the business conflict unresolved.
• Local preservation may support application needs, but it does not create a governed enterprise status for the master hub.

Question 2

Topic: Master Reference and Architecture Governance

A data architecture review finds a conflict between a shared enterprise model and a project model for customer data.

Which governance gap is most directly indicated?

Options:

• A. Insufficient database performance tuning standards

• B. Incomplete report certification for customer metrics

• C. Poor identity administration for application users

• D. Weak model reuse and lineage governance for shared entities

Best answer: D

Explanation: The core issue is architecture and modeling governance. A project has created a local customer structure that duplicates a governed enterprise entity, uses a different identifier, and lacks lineage to the mastered source. That points to a gap in standards or review controls for reusing shared data models, mapping project models to enterprise models, and confirming accountable ownership before implementation. Data governance should ensure that architecture decisions support consistency, reuse, traceability, and clear ownership across initiatives. Technical teams may implement the model, but governance sets the decision rights and escalation path when a project diverges from an authoritative model. Performance, reporting, and access administration do not address the observed duplication and missing lineage.

• Performance tuning is unrelated because the finding concerns semantic consistency and ownership, not query speed or storage design.
• Report certification would apply to approved business measures, but no conflicting report metric is described.
• Identity administration manages user access, while the issue is conflicting data models and missing lineage.

Question 3

Topic: Master Reference and Architecture Governance

An enterprise revenue report is no longer trusted because regions use different local customer-status codes and the customer master contains duplicate records for the same legal entities. The BI team can map codes temporarily, but no enterprise authority owns the approved code set or duplicate-handling rules. What governance action should occur first?

Options:

• A. Ask each region to publish its local code list in the catalog

• B. Hard-code regional code mappings in the reporting layer

• C. Approve enterprise code and survivorship standards through assigned owners and stewards

• D. Delete duplicate customer records directly from source systems

Best answer: C

Explanation: Uncontrolled local codes and duplicate master records are governance issues before they are technical cleanup tasks. The organization needs accountable decision rights for reference data standards, master-data matching, survivorship, and exception handling. Data owners and stewards should approve the enterprise code set and the rules for identifying and resolving duplicate customer records, with escalation to the governance council if business units disagree. BI mappings or database cleanup may be useful later, but they should implement governed decisions rather than create unofficial reporting logic. The key distinction is between temporary technical workarounds and governed ownership of enterprise master and reference data.

• Reporting-layer mapping may mask symptoms, but it does not establish authoritative codes or ownership of the rules.
• Direct deletion risks removing valid records without approved match, merge, and survivorship criteria.
• Cataloging local codes improves visibility, but documentation alone does not resolve conflicting enterprise definitions.

Question 4

Topic: Master Reference and Architecture Governance

A claims modernization program proposes a new logical data model with an entity named Insured Party. The enterprise data model and business glossary already define Customer as “a person or organization that has a current or historical relationship with the company,” and the customer data owner reports that claims, billing, and CRM use that definition for reporting. Which governance action best aligns the model decision with enterprise standards and business definitions?

Options:

• A. Escalate directly to executive leadership to mandate the CRM naming convention.

• B. Convene stewardship and architecture review to map the entity to the approved definition.

• C. Ask the database administrator to rename the physical table after deployment.

• D. Let the project data modeler create a claims-specific definition.

Best answer: B

Explanation: Architecture and modeling governance should connect model decisions to approved business definitions, enterprise data models, and stewardship authority. Here, the issue is not only naming; it affects whether claims data will align with shared customer meaning across reporting and integration. The appropriate response is a governed review involving the relevant data owner, data stewards, and architecture/modeling governance forum. They can confirm whether Insured Party is a subtype, synonym, role, or distinct concept, then document the approved model change or exception. Technical renaming alone does not resolve semantic alignment.

• Creating a local claims definition weakens enterprise consistency when a governed definition already exists.
• Renaming a physical table after deployment treats the problem as technical custody rather than semantic governance.
• Mandating the CRM convention skips stewardship analysis and may confuse naming with approved enterprise meaning.

Question 5

Topic: Master Reference and Architecture Governance

A bank has an approved enterprise customer data model, but the lending and marketing programs have each created separate customer structures with different identifiers and definitions. A regulatory risk report now requires traceable lineage from source systems to the report. The architecture team can document models but has no authority to require reuse, and no business owner has been named for the shared customer domain. Which governance decision is BEST?

Options:

• A. Have the architecture team merge both models into a single design

• B. Assign a customer data owner and stewards with reuse and lineage decision rights

• C. Make the database administration team the owner of customer identifiers

• D. Allow both programs to continue and add mappings in the metadata catalog

Best answer: B

Explanation: An architecture conflict over a shared data domain is not solved only by producing another model. The visible gap is that no accountable business owner or stewardship structure can decide what the customer domain means, which identifiers are authoritative, when reuse is required, and what lineage evidence must be maintained. Data governance should establish decision rights and escalation through the governance operating model, then use architecture and metadata practices to implement the agreed standard. This preserves consistency and reuse while supporting regulatory lineage needs. Technical teams can document and implement decisions, but they should not become the authority for cross-domain business definitions.

• Model merging treats the symptom as a design task but does not create authority to resolve cross-domain definition and identifier conflicts.
• Catalog mappings may improve visibility, but they preserve inconsistent structures and do not address reuse or ownership.
• Database administration ownership confuses technical custody with business accountability for shared customer meaning and identifiers.

Question 6

Topic: Master Reference and Architecture Governance

A company is preparing to certify a revenue dashboard built from CRM, billing, and product data. Sales and Finance disagree on the definition of recurring revenue, Customer Operations disputes the customer-status mapping, and an audit finding requires documented approval for certified BI assets. The BI team owns the warehouse pipelines, but the governance charter assigns cross-domain business data decisions to data owners through the data governance council. What is the best governance decision?

Options:

• A. Have the relevant data owners approve through the governance council

• B. Allow Finance to approve because revenue is a financial measure

• C. Ask each analyst team to document its preferred definition

• D. Let the BI engineering lead certify the dashboard after testing

Best answer: A

Explanation: BI and integration governance separates business approval from technical implementation. The warehouse or BI team may build pipelines, test transformations, and publish assets, but disputed mappings and metric definitions are business semantic decisions. Because the issue crosses CRM, billing, product, Sales, Finance, and Customer Operations, the appropriate approval path is through accountable data owners using the data governance council. Data stewards should prepare the glossary entries, mapping documentation, lineage, quality evidence, and certification package, while technical custodians implement the approved rules. Certification should not be a local project or tool-administration decision when auditability and cross-domain agreement are required.

The key distinction is decision rights: owners approve meaning and certification; custodians execute and maintain the technical assets.

• BI-only certification fails because technical testing does not resolve contested business definitions or provide accountable semantic approval.
• Finance-only approval is too narrow because the mapping and metric depend on multiple business domains, not only financial reporting.
• Local analyst definitions increase inconsistency and do not create a governed, certified BI product.

Question 7

Topic: Master Reference and Architecture Governance

A product analytics initiative wants to build a new customer behavior data store. The proposed logical model creates a separate customer_key, and the integration design uses direct feeds from CRM and billing instead of the approved customer master and integration pattern. The business sponsor says the design is faster, but customer definitions would differ from enterprise reporting. What should the data governance lead do next?

Options:

• A. Approve the design if the analytics team documents the fields

• B. Let the project proceed and reconcile definitions in reports

• C. Ask database administrators to tune the physical schema

• D. Route the design for architecture review and exception escalation

Best answer: D

Explanation: Architecture and modeling governance should be engaged when a proposed model, data store, or integration pattern conflicts with approved enterprise models, master data usage, or integration standards. The issue is not just technical implementation speed; it affects decision rights, shared definitions, lineage, and consistency of customer data across the organization. A suitable response is to send the design through the architecture or modeling review process, involve the relevant data owner and stewards, and escalate any requested exception to the proper governance forum if the conflict cannot be resolved within standards.

Documenting fields or fixing reports later does not address the governance decision about whether a competing customer key and bypassed master data pattern are acceptable.

• Documentation alone records the design but does not resolve the conflict with approved customer definitions and integration standards.
• Physical tuning addresses performance or storage concerns, not governance approval of the logical model or integration pattern.
• Report reconciliation pushes the problem downstream and allows inconsistent customer definitions to become embedded.

Question 8

Topic: Master Reference and Architecture Governance

A bank finds that three applications use different values for customer relationship type. The CRM team uses Retail, SMB, and Enterprise; billing uses numeric codes; and reporting applies its own mapping each month. Executives want the monthly revenue dashboard to use one trusted definition going forward. Which response best fits master/reference data governance?

Options:

• A. Establish governed reference values and cross-system ownership

• B. Run a one-time script to standardize current report values

• C. Ask each application team to clean its own lookup table

• D. Let the dashboard team maintain the monthly mapping

Best answer: A

Explanation: Master and reference data governance applies when shared data values affect multiple business processes, systems, or reports. Customer relationship type is not just a local application setting because inconsistent values change enterprise revenue reporting. The appropriate response is to define governed reference values, assign accountable business ownership and stewardship, document approved mappings, and manage changes through a controlled process. Local maintenance may still update lookup tables, and cleanup may still correct existing records, but those actions should follow the governed definition rather than replace it. A one-time cleanup fixes symptoms; governance prevents the inconsistency from recurring.

• Local lookup cleanup treats the values as separate application maintenance and misses the need for shared definitions and decision rights.
• One-time scripting may repair current report output but does not create ownership, standards, or change control.
• Dashboard-owned mapping leaves a reporting team compensating for upstream inconsistency instead of governing the reference data at the enterprise level.

Question 9

Topic: Master Reference and Architecture Governance

A bank is building a new customer data mart. The project model uses client, while the enterprise business glossary defines customer as a party with at least one active product. Marketing wants prospects included, Risk wants only active product holders, and the data architecture standard requires conformed entity names and approved definitions before publishing shared models. What is the best governance decision?

Options:

• A. Create separate marts for Marketing and Risk to avoid a shared definition

• B. Escalate the definition conflict to the governance council and require steward-approved model alignment

• C. Allow the project team to publish client and document it as a local synonym

• D. Ask data architects to rename client to customer without changing scope

Best answer: B

Explanation: Architecture and modeling governance should ensure shared data models conform to enterprise standards and approved business definitions. Here, the issue is not only a naming preference; Marketing and Risk have conflicting meanings for the same core party concept, and the model is intended for a shared data mart. The appropriate governance response is to use the defined decision rights: data stewards clarify and recommend definitions, and the governance council resolves cross-domain conflicts when business areas cannot agree. Publication should wait until the model, glossary term, and metadata are aligned. A purely technical rename or local synonym would leave the underlying semantic conflict unresolved.

• Local synonym fails because it bypasses the standard for shared models and preserves conflicting meanings.
• Technical rename fails because changing the label does not resolve whether prospects are in scope.
• Separate marts fails because it avoids governance of a shared business concept and may increase inconsistency.

Question 10

Topic: Master Reference and Architecture Governance

Two transformation projects are designing different data structures for the shared business concept “Customer.” One uses separate retail and commercial customer tables; the other proposes a single party model with customer roles. Both projects need approval to proceed, and downstream analytics will consume the shared data. What is the best governance response?

Options:

• A. Allow each project to proceed if mappings are documented

• B. Ask database administrators to merge the tables during implementation

• C. Let the analytics team choose the model it prefers

• D. Escalate the conflict to architecture governance for a common canonical model decision

Best answer: D

Explanation: When projects define incompatible structures for the same shared business concept, governance should prevent parallel local designs from becoming enterprise inconsistency. The issue belongs in architecture and modeling governance, with business ownership and stewardship input, because the decision affects meaning, integration, lineage, quality rules, and downstream use. A governed canonical or enterprise-aligned model decision gives projects a common target and records the rationale, standards, and exceptions if needed. Documentation and mappings may be useful after the decision, but they do not resolve the conflicting semantics or decision rights by themselves.

• Mappings only may hide the conflict temporarily but leaves inconsistent structures and definitions in place.
• Analytics preference shifts an enterprise design decision to one consuming team rather than the proper governance forum.
• DBA merge work treats the issue as technical implementation, not as a governed modeling and ownership decision.

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
• Glossary and Metadata Governance
• Data Quality Governance
• Security and Compliance Alignment
• Governance Metrics Maturity and Improvement
• Governance Program Operations