Free DAMA CDMP Fundamentals Practice Questions: Data Architecture

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: Data Architecture

A bank is launching a digital lending strategy. Executives want a shared view that links the strategy to the lending capabilities, origination and approval processes, supporting applications, key data stores, and integration patterns between systems. Which enterprise data architecture artifact best fits this need?

Options:

• A. Physical database indexing standard

• B. Loan application data quality rulebook

• C. Dashboard design guide for lending reports

• D. Enterprise data architecture roadmap and capability map

Best answer: D

Explanation: Enterprise data architecture provides the organizing view that aligns data assets and flows with business direction. For the digital lending initiative, the useful artifact must show how business strategy depends on capabilities, how those capabilities are executed through processes, which applications and data stores support them, and how data moves across the environment. A roadmap and capability-oriented architecture view is appropriate because it supports planning, gap analysis, prioritization, and communication across business and technology stakeholders. More detailed artifacts may be needed later, but they do not provide the cross-enterprise alignment requested.

• Indexing standard focuses on physical database performance and implementation consistency, not strategic alignment across capabilities and systems.
• Quality rulebook helps define and monitor valid lending data, but it does not map strategy to applications, stores, and integrations.
• Dashboard guide supports BI presentation consistency, but it does not describe the enterprise data landscape behind the lending capability.

Question 2

Topic: Data Architecture

A retailer is modernizing its customer analytics environment. Executives want to trace how the strategy to improve omnichannel customer experience depends on business capabilities, order and service processes, applications, data stores, and data movement between systems. Which deliverable best represents enterprise data architecture alignment?

Options:

• A. A source-to-target mapping for one customer data feed

• B. A physical table design for the customer analytics database

• C. A capability-to-data map linking processes, applications, stores, and integration patterns

• D. A dashboard catalog listing report owners and refresh schedules

Best answer: C

Explanation: Enterprise data architecture provides a business-aligned view of how data supports organizational strategy. It connects business capabilities and processes to the data subject areas, applications, data stores, and integration patterns that enable them. In this scenario, the need is cross-enterprise alignment for omnichannel customer experience, not the design of one database, report, or data feed. A capability-to-data map is the most fitting deliverable because it shows how strategic intent is realized through data assets and information flows across the application landscape. The key distinction is scope: enterprise data architecture explains business-data-system relationships across the organization, while more detailed designs describe individual implementations.

• Physical table design is too implementation-specific and does not show enterprise strategy, capabilities, or integration patterns.
• Dashboard catalog supports BI metadata and ownership, but it does not map business capabilities to data architecture.
• Single feed mapping supports integration detail for one flow, but it lacks the enterprise-wide alignment view.

Question 3

Topic: Data Architecture

A retailer’s customer analytics program keeps finding inconsistent customer counts in loyalty, e-commerce, and store operations reports. Each team has corrected its own database views, but new initiatives continue to define “active customer” differently because project plans are not tied to common business capabilities or an enterprise data roadmap. Which action best fits the root cause?

Options:

• A. Create a one-time customer-count reconciliation report

• B. Rebuild the loyalty reporting view

• C. Increase indexing on customer tables

• D. Conduct an enterprise data architecture alignment review

Best answer: D

Explanation: A data architecture alignment issue appears when problems recur across projects, subject areas, or business processes because data concepts are not connected to the enterprise’s business capabilities, strategy, and roadmap. In this scenario, local database and report fixes have not solved the inconsistency because each initiative continues to define a core business concept differently. The appropriate response is to review and align enterprise data architecture with business stakeholders, shared definitions, governance, and roadmap priorities. A single report repair may reduce one symptom, but it will not address the architectural cause.

• Report rebuild treats the loyalty report as the defect, but the inconsistency spans multiple channels and new initiatives.
• Indexing addresses query performance, not conflicting business definitions or architecture alignment.
• One-time reconciliation may explain a current variance, but it does not prevent future projects from defining customer differently.

Question 4

Topic: Data Architecture

A financial services company has separate lending, deposits, and risk teams that define customer and account data differently. Each project creates its own mappings and point-to-point interfaces, causing duplicated integration work and inconsistent reporting. Which architectural response best improves consistency and reuse across the business domains?

Options:

• A. Add more report-level reconciliations after data is loaded

• B. Define an enterprise data architecture with shared subject areas and standards

• C. Create a separate physical database design for each project

• D. Assign database administrators to tune the existing interfaces

Best answer: B

Explanation: Enterprise data architecture aligns data across business domains by defining shared subject areas, common principles, standards, and target-state guidance. In this scenario, the main problem is not a single report defect or a database performance issue; it is inconsistent meaning and duplicated integration across lending, deposits, and risk. A cross-domain architectural response gives projects a common frame for data definitions, reuse, access patterns, governance expectations, and integration design. It supports local delivery while reducing fragmentation.

Project-specific physical designs, report reconciliations, and interface tuning may solve local symptoms, but they do not establish reusable enterprise alignment.

• Project-specific design preserves local variation and does not address enterprise consistency across domains.
• Report reconciliation detects downstream differences but does not prevent inconsistent definitions or duplicated mappings.
• Interface tuning may improve performance, but it does not resolve semantic inconsistency or reuse problems.

Question 5

Topic: Data Architecture

A company has several business units building separate customer data stores. Each unit uses different customer definitions, local codes, and project-specific interfaces. Leadership wants an architecture recommendation that will support durable data sharing, clear stewardship, common standards, and reuse across future initiatives. Which recommendation best addresses this need?

Options:

• A. Create an enterprise customer subject-area view with standard definitions, authoritative sources, and stewardship assignments

• B. Design a physical schema optimized for the largest customer database

• C. Build point-to-point mappings between each current customer application

• D. Create separate reporting marts for each business unit

Best answer: A

Explanation: Data architecture artifacts should provide stable enterprise views of data assets, not only project-level technical designs. For durable sharing and reuse, the architecture should clarify common business concepts, standard definitions, authoritative sources, ownership or stewardship, and how data domains relate across the enterprise. A subject-area or enterprise data view is well suited because it guides consistent design decisions across many systems and future initiatives. Point-to-point interfaces, physical schemas, and local reporting marts may solve immediate delivery needs, but they do not establish shared meaning or enterprise standards.

• Point-to-point integration solves immediate connectivity but usually increases coupling and does not create durable shared definitions.
• Physical optimization focuses on one implementation and does not address enterprise meaning, stewardship, or reuse.
• Separate reporting marts may serve local analytics but can preserve inconsistent definitions across business units.

Question 6

Topic: Data Architecture

A retail company is launching an omnichannel strategy that requires consistent customer, product, and inventory information across stores, e-commerce, and marketing analytics. Each operational database passes its local tests, but initiatives repeatedly stall because teams use different business concepts, duplicate integrations, and conflicting priorities for shared data. Governance is informal, and executives want a reusable approach rather than another report fix. Which action is the BEST professional decision?

Options:

• A. Tune the slowest operational database queries

• B. Establish an enterprise data architecture aligned to business capabilities

• C. Rebuild the executive sales dashboard

• D. Add more validation rules to each source system

Best answer: B

Explanation: Data architecture aligns data assets, flows, standards, and integration direction with business strategy and capabilities. In this scenario, the local databases are functioning, but the business cannot execute an omnichannel strategy because shared data concepts, priorities, and integrations are not coordinated across domains. That points to an enterprise data architecture alignment issue. A suitable response is to define architecture principles, subject areas, target data flows, shared definitions, and a roadmap governed with business stakeholders. Fixing one report, query, or source-system rule may reduce a local symptom, but it will not create reusable alignment for customer, product, and inventory data across the enterprise.

• Database tuning treats the problem as local performance, but the stated failures involve meaning, priorities, and reuse across domains.
• Dashboard rebuilding addresses a reporting symptom, not the architecture needed for consistent enterprise data.
• Source validation may improve local data capture, but it does not resolve duplicated integrations or conflicting business concepts.

Question 7

Topic: Data Architecture

After a merger, three applications maintain a Customer Status value. Executives cannot tell which application is authoritative or how the value reaches billing, CRM, and the data warehouse. Which data architecture artifact would best clarify this uncertainty?

Options:

• A. Data quality scorecard for customer status

• B. Source-to-target lineage and data-flow map

• C. Enterprise conceptual subject-area model

• D. Physical database schema for customer tables

Best answer: B

Explanation: A lineage and data-flow artifact is the strongest fit when the uncertainty is about authoritative source and movement across systems. It connects source systems, transformations, interfaces, and consuming platforms, often identifying the system of record for a data element. A conceptual subject-area model is useful for enterprise scope and major business concepts, but it normally does not show operational movement or source authority. A physical schema describes table structures inside a platform, and a quality scorecard measures fitness of data against rules. The key distinction is whether the artifact explains cross-system origin and flow, not just definition, structure, or quality results.

• Subject-area view helps frame enterprise concepts, but it does not trace Customer Status through applications.
• Physical schema shows implementation details in one database, not authoritative ownership across systems.
• Quality scorecard may reveal inconsistent values, but it does not identify the system of record or integration path.

Question 8

Topic: Data Architecture

A regional insurer is starting a data architecture effort after teams used different definitions for customer, policy, and claim data. Business stewards need a shared view of major data groupings and boundaries before approving integration work. The architecture team must stay at a business-concept level and avoid physical database design. Which artifact is the BEST professional decision to create first?

Options:

• A. Subject-area model

• B. Architecture roadmap

• C. Data inventory

• D. Data-flow view

Best answer: A

Explanation: A subject-area model is a data architecture artifact used to organize high-level business data domains, such as customer, policy, and claim, and show how they relate at a conceptual level. It is useful early in architecture work because it gives business stewards a common language for discussing scope, ownership, and integration priorities without requiring table structures, keys, or platform choices. A data inventory would list existing data assets, a data-flow view would show movement between systems, and a roadmap would sequence future initiatives. Here, the immediate need is conceptual alignment on major data groupings and boundaries.

• Asset listing is not enough because an inventory identifies existing data stores or assets rather than defining business subject boundaries.
• System movement comes later because a data-flow view shows where data moves, not the conceptual grouping of core business data.
• Initiative sequencing is premature because a roadmap depends on architectural scope and priorities that have not yet been clarified.

Question 9

Topic: Data Architecture

A regional insurer has separate policy data stores for underwriting, claims, and finance. Each area defines “active policy” differently, and executives no longer trust cross-functional reports because totals conflict. The CIO asks the data architecture team to set the first priority for an enterprise alignment initiative. Which priority best fits this need?

Options:

• A. Define enterprise data domains, shared definitions, and authoritative sources

• B. Create a new dashboard with reconciled executive totals

• C. Assign each department to maintain its own policy definition

• D. Move all policy data into one physical database

Best answer: A

Explanation: Enterprise data architecture aligns data assets with business capabilities, shared semantics, and trusted decision needs. When duplicated stores and inconsistent definitions damage trust, the priority is to establish common data domains, agreed business definitions, authoritative sources, and architecture principles for reuse and integration. That creates a stable target for later work such as integration, warehousing, data quality remediation, and reporting design. A single platform or new dashboard may help later, but it does not resolve conflicting meaning or ownership of critical business data.

• Dashboard-first thinking hides the semantic conflict instead of resolving why report totals differ.
• Single database assumption treats physical consolidation as the main issue, but architecture alignment may use federated or integrated sources.
• Department-only definitions preserve local inconsistency and weaken enterprise trust in shared reporting.

Question 10

Topic: Data Architecture

A manufacturer has separate sales, finance, and customer-service data marts that each store customer and product data. Executives do not trust monthly revenue and customer profitability reports because definitions of customer, active product, and net revenue differ by department. From an enterprise data architecture alignment perspective, what should be prioritized first?

Options:

• A. Define enterprise subject areas, authoritative sources, and shared business definitions

• B. Let each application team maintain its own local data dictionary

• C. Redesign dashboard layouts around each department’s preferred metrics

• D. Increase data replication frequency between departmental data marts

Best answer: A

Explanation: Enterprise data architecture aligns data assets with business capabilities and decision needs. When trust is damaged by duplicated stores and inconsistent meanings, the priority is to create a shared architectural view of core subject areas, authoritative sources, key data flows, and common business definitions. This does not replace data governance, but it gives governance and implementation teams a coherent target state for reporting, integration, and stewardship decisions.

Improving dashboards or moving data faster may make inconsistent data more visible, but it does not resolve the underlying architectural problem: the organization lacks a common view of what the data means and where it should be mastered.

• Dashboard redesign changes presentation, but conflicting definitions would still produce inconsistent results.
• Faster replication improves timeliness, not semantic consistency or source authority.
• Local dictionaries may document differences, but they preserve departmental silos instead of aligning enterprise meaning.

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