Free DAMA CDMP Fundamentals Practice Questions: Data Integration and Interoperability

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 Integration and Interoperability

A regional health network is integrating patient referral data across hospitals, clinics, and an external care-management partner. Each system can send files successfully, but the receiving teams still disagree on what “active patient” means, use different patient identifiers, and apply different code sets for referral status. Which practice best supports interoperability for this initiative?

Options:

• A. Create shared semantic standards and governance for exchanged data

• B. Add more dashboard filters for referral reports

• C. Increase the frequency of file transfers between systems

• D. Move all data into one operational database

Best answer: A

Explanation: Interoperability is more than technical connectivity. In this scenario, the files already move between systems, but the organizations do not share definitions, identifiers, code sets, or decision rights for the exchanged data. A shared semantic and standards approach addresses those gaps by defining common business meanings, accepted data formats, identifier matching rules, controlled vocabularies, interface expectations, and governance for changes or disputes. This allows each system and organization to interpret referral data in the same way. Simply improving transport or reporting does not resolve inconsistent meaning.

• Transfer frequency improves timeliness but does not fix conflicting definitions, identifiers, or code sets.
• Single database may reduce some integration complexity, but it is often unrealistic and does not replace cross-organization standards and governance.
• Dashboard filters may help users slice reports, but they do not create semantic consistency across source systems.

Question 2

Topic: Data Integration and Interoperability

A bank discovers that the same customer-status transformation is coded separately in an ETL job, two regulatory reports, an API interface, and several analyst extracts. The versions are starting to produce inconsistent results. Which response best fits a DAMA-aligned data integration practice?

Options:

• A. Move all reporting to a new dashboard tool

• B. Let each consuming team maintain its own version

• C. Increase reconciliation checks after each run

• D. Define and govern a reusable transformation rule

Best answer: D

Explanation: When transformation logic is duplicated across data movement paths and consumption layers, the priority is to establish a single governed definition of the rule and make it reusable through integration design, metadata, and stewardship controls. In DAMA-aligned practice, this may involve a common source-to-target mapping, shared business rule, reusable integration component, or governed semantic layer, depending on architecture. The key is that the transformation is defined once, approved by accountable business and technical roles, documented in metadata, and reused consistently. Reconciliation can detect differences, but it does not remove the root cause. Tool replacement also does not solve inconsistent rule ownership by itself.

• Local ownership preserves the duplication that caused inconsistent customer-status results.
• Dashboard replacement changes the presentation layer but does not govern transformation logic used by ETL jobs, APIs, and extracts.
• More reconciliation may find mismatches after processing, but it does not create a reusable standard rule.

Question 3

Topic: Data Integration and Interoperability

A retailer loads orders from its e-commerce platform and ERP system into a data warehouse through a shared staging area. Auditors need to trace each warehouse order amount to the original source record, the load run, and the transformation rule that changed the amount. Which control point best fits this need?

Options:

• A. Add referential integrity checks in the warehouse

• B. Compare monthly finance totals after reporting

• C. Document dashboard calculations in the BI catalog

• D. Capture lineage metadata in the integration pipeline

Best answer: D

Explanation: Lineage capture is strongest at the data movement and transformation control point because that is where source records are selected, mapped, transformed, and loaded. In this scenario, auditors need evidence that connects the warehouse amount to the source record, the specific load run, and the rule that changed the value. Capturing that metadata in the integration pipeline or staging process creates repeatable, record-level traceability. Downstream documentation can help users understand reports, and reconciliation can detect aggregate differences, but neither reliably records how each value was produced.

• BI catalog documentation helps explain report metrics, but it does not prove record-level movement and transformation history.
• Referential integrity checks validate relationships, but they do not capture the rule or run that changed an amount.
• Monthly total comparison is useful reconciliation, but it is too late and too aggregated for audit lineage.

Question 4

Topic: Data Integration and Interoperability

Three regional policy systems must send customer and policy status data to a new claims analytics service. The business needs comparable status reporting within 6 months. The source systems cannot be replaced, status values such as “active” and “closed” have different meanings by region, and auditors need traceability of transformations. Which decision best addresses the interoperability problem?

Options:

• A. Store raw source extracts and let analysts interpret status values.

• B. Rename all feed fields to match the analytics service.

• C. Build separate point-to-point transformations for each source feed.

• D. Implement a governed canonical exchange standard with shared definitions and code mappings.

Best answer: D

Explanation: Semantic interoperability requires systems to exchange data with a shared understanding of meaning, not just compatible file formats or field names. In this situation, the main risk is inconsistent interpretation of status values across regions. A governed canonical exchange standard, supported by business definitions and approved code mappings, gives each source a traceable way to translate local meanings into common enterprise meanings. It also fits the constraint that existing systems cannot be replaced. Point-to-point transformations may move data, but they are harder to govern consistently and audit across multiple feeds. The key is to standardize meaning and transformation rules, not merely centralize or rename data.

• Point-to-point logic may connect the systems, but it risks inconsistent mapping rules and weak reuse across regions.
• Raw extracts preserve source detail, but they shift semantic interpretation to analysts and do not create comparable reporting.
• Field renaming improves superficial consistency, but it does not resolve different business meanings for the same status values.

Question 5

Topic: Data Integration and Interoperability

A retailer has connected its e-commerce, store POS, and finance systems through a new integration platform. The feeds load on schedule with no technical errors, but executives still see different revenue totals by channel, customer records are duplicated, and some refunds are posted differently across systems. Which action best addresses the integration problem?

Options:

• A. Define shared semantics and cross-system mapping rules

• B. Add more dashboard filters for each channel

• C. Increase the integration job frequency

• D. Move all feeds to a larger storage platform

Best answer: A

Explanation: Technical connectivity does not guarantee interoperability. In this case, data moves successfully, but the systems do not share consistent meanings for revenue, customer identity, and refund handling. The best response is to establish semantic consistency through agreed business definitions, standard identifiers, source-to-target mappings, transformation rules, and stewardship review for disputed meanings. This work may involve data governance, master data practices, and reference standards, but the immediate integration need is to make exchanged data consistently interpretable across systems.

Improving schedules, storage, or report presentation can support operations, but they do not resolve conflicting definitions or duplicate identity rules.

• Faster loading fails because more frequent feeds can replicate inconsistent meanings more often.
• Bigger storage fails because capacity does not reconcile business definitions or customer identity.
• Dashboard filters fail because presentation controls hide symptoms rather than correcting semantic inconsistency.

Question 6

Topic: Data Integration and Interoperability

A regional insurer is integrating eligibility data from three partner networks. Each partner uses its own member identifiers, plan status codes, date formats, and definition of “active coverage.” The insurer needs reliable automated exchange while allowing partners to keep their internal applications. Which interoperability control best fits this need?

Options:

• A. Faster file transfer schedule for all feeds

• B. New dashboard showing partner data side by side

• C. Shared canonical exchange specification with mappings

• D. Central database replacing all partner applications

Best answer: C

Explanation: Interoperability depends on more than moving data between systems. When partners use different identifiers, code values, formats, and business meanings, the control should define how exchanged data is interpreted consistently. A shared canonical exchange specification can include business definitions, standard field formats, controlled code-set mappings, identifier crosswalks, and transformation rules. This allows each partner to retain its internal systems while making the exchanged data understandable and usable by the receiving organization. A technical transport improvement alone would not resolve semantic inconsistency.

• Dashboard comparison may expose differences, but it does not standardize exchanged meanings or automate consistent interpretation.
• System replacement is unnecessarily disruptive and does not fit the stated need to let partners keep internal applications.
• Faster transfers improve timeliness, but they do not resolve mismatched identifiers, formats, codes, or definitions.

Question 7

Topic: Data Integration and Interoperability

A retailer integrates daily sales data from point-of-sale systems into a staging area, then loads a warehouse fact table used by finance reports. Finance requires row counts and sales totals to agree from the source extract through reporting. Where should reconciliation controls be placed?

Options:

• A. At each major data movement handoff

• B. Only during the initial warehouse migration

• C. Only in the final finance reports

• D. Only between the operational source systems

Best answer: A

Explanation: Reconciliation in data integration checks that data remains complete and consistent as it moves between environments and uses. When integrated data must agree across source, staging, target, and reports, controls should be applied at the key handoffs: source-to-extract, extract-to-staging, staging-to-target, and target-to-reporting. Typical checks include record counts, control totals, balancing rules, rejected-record logs, and exception review. Limiting reconciliation to one layer can hide defects introduced earlier or later in the flow. The key takeaway is that reconciliation follows the movement of data, not just the final consumer view.

• Final reports only can detect visible reporting differences but may not identify where data was lost or transformed incorrectly.
• Source-only checks confirm operational agreement but do not validate extraction, staging, warehouse loading, or reporting transformations.
• Initial migration only treats reconciliation as a one-time activity, but recurring data movement needs recurring controls.

Question 8

Topic: Data Integration and Interoperability

A retailer wants near-real-time inventory availability on its website after sales occur in stores and online. The source sales systems must remain operational during business hours, and the website only needs a small set of product and stock fields rather than full transactional history. Which integration pattern is the best professional decision?

Options:

• A. Streaming event-based integration

• B. Manual API polling by the website

• C. Full database replication

• D. Nightly batch file transfer

Best answer: A

Explanation: Streaming event-based integration is suited to continuously moving small, time-sensitive changes, such as sales or stock adjustments, from operational systems to consuming applications. It supports low-latency availability while avoiding the need to copy full transaction histories. In this situation, the website needs current inventory fields, not complete sales records, and the sales systems should not be heavily queried during operating hours. A controlled event stream or message-based feed can publish relevant changes as they occur and allow downstream services to update product availability. Batch transfer is simpler but introduces delay, while full replication moves more data than needed and can increase operational and governance complexity.

• Nightly batch transfer fails because it cannot meet the near-real-time inventory requirement.
• Full replication moves unnecessary transactional data and adds avoidable complexity for a narrow website use case.
• Manual API polling can increase source-system load and is less reliable than publishing changes as events.

Question 9

Topic: Data Integration and Interoperability

A retailer is integrating customer and order data from CRM and billing systems into a data warehouse for monthly revenue reporting. The CRM and billing systems use different customer status codes, report totals must reconcile to finance source totals, and the data governance team needs lineage for critical fields. The source applications cannot be changed this quarter. Which control point is the best professional decision?

Options:

• A. BI dashboard calculation layer

• B. Source application data-entry screens

• C. Manual finance spreadsheet after reporting

• D. Integration staging layer before warehouse loading

Best answer: D

Explanation: For integration patterns and data movement, the strongest control point is usually where data is received, standardized, and prepared for downstream use. In this case, the organization cannot change source systems, but it must harmonize status codes, validate data, reconcile totals to finance sources, and preserve lineage for critical fields. An integration staging layer before the warehouse load supports these needs without forcing changes into operational applications. It also prevents inconsistent transformations from being repeated in multiple reports. Controls placed only in dashboards or manual month-end workarounds are too late in the lifecycle and do not create a reusable, governed integration process.

• Source screens are not feasible because the applications cannot be changed this quarter.
• Dashboard calculations are too late because they do not reliably control source-to-target reconciliation or reusable lineage capture.
• Manual spreadsheets may detect discrepancies, but they do not provide a governed integration control point for recurring data movement.

Question 10

Topic: Data Integration and Interoperability

A regional health network is building a shared reporting feed across four partner systems. The partners use different patient identifiers, diagnosis code sets, date formats, and definitions for “encounter.” They need comparable quarterly reporting, but none can replace its source application this year. Which action is the best professional decision?

Options:

• A. Require every partner to adopt one source application

• B. Create governed semantic mappings and shared data standards

• C. Convert all files to the same technical format

• D. Use the largest partner’s definitions as the default

Best answer: B

Explanation: Interoperability requires more than moving data or standardizing file syntax. In this situation, the main problem is semantic consistency across partners: identifiers, code values, formats, and business definitions do not align. A governed interoperability control should define shared business terms, identifier matching or cross-reference rules, accepted code mappings, format standards, and source-to-target transformation rules. This allows partners to keep their current applications while producing comparable reporting data. Technical format conversion may be part of the implementation, but it does not resolve conflicting meanings. The key takeaway is to control both syntax and semantics when integrated data must be compared across organizations.

• Single application mandate fails because the partners cannot replace their source applications this year.
• Technical format conversion helps with syntax, but it does not reconcile identifiers, code values, or business definitions.
• Largest partner default may be expedient, but it is not a governed agreement across stakeholders and can bias reporting 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
• Data Architecture
• Document and Content Management
• Data Ethics
• Data Governance
• Master and Reference Data Management
• Data Modelling and Design
• Data Quality
• Data Security
• Data Storage and Operations
• Data Warehousing and Business Intelligence
• Metadata Management