DAMA Updated DQ-1220 Exam Questions and Answers by nikodem

A primary business driver for establishing a Data Quality Management program is to reduce the risks and costs associated with poor-quality data. DAMA-DMBOK2 treats low-quality data as a direct source of operational cost and organizational risk. The Chapter 13 business drivers include increasing the value of organizational data, reducing risks and costs caused by poor quality, improving efficiency and productivity, and protecting organizational reputation.

Poor-quality data generates both visible and hidden costs. Examples include rework, manual correction, incorrect invoices, failed customer interactions, regulatory exposure, inappropriate decisions, integration delays, missed opportunities, and reputational damage. DMBOK2 further emphasizes that low-quality data represents cost and risk rather than value, making Data Quality management necessary throughout the data lifecycle.

A formal DQ program addresses these consequences through defined requirements, profiling, measurement, root-cause analysis, corrective and preventive action, monitoring, and governance. The purpose is therefore broader than making the DQ team efficient or supporting a specific technology initiative such as warehouse consolidation.

The economic and risk-reduction argument also provides the strongest basis for executive sponsorship because improvements can be linked directly to measurable business outcomes.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Business Drivers; Costs of Poor Data Quality; Risk Reduction; Data Quality Program; Data Quality Lifecycle.

===============

The need to manage data movement efficiently is a primary business driver for Data Integration and Interoperability (DII). DAMA-DMBOK2 states this directly. Modern organizations operate hundreds or thousands of databases, applications, files, services, data stores, external interfaces, and analytical platforms. Data must continually move among these environments, often across organizational boundaries.

Without disciplined integration management, data movement becomes fragmented, expensive, difficult to monitor, and highly dependent on duplicated point-to-point interfaces. DII addresses this problem by establishing controlled mechanisms for extraction, transformation, messaging, replication, orchestration, APIs, data virtualization, and other forms of information exchange.

From a Data Quality perspective, every movement of data presents an opportunity either to preserve quality or to damage it. Source-to-target mappings must maintain semantic meaning, transformations must be controlled, reference values must remain consistent, and lineage must show how values were altered.

Metadata Management therefore records mappings, interface definitions, transformation rules, and lineage. Master Data Management uses integration mechanisms to distribute governed master and reference data consistently between systems.

Data Warehousing is a major consumer of integration capabilities, but the broader discipline whose explicit driver is efficient movement across systems is Data Integration and Interoperability.

Reference Topics: DAMA-DMBOK2 Chapter 8 — Business Drivers; Data Integration and Interoperability; Data Movement; Chapter 13 — Consistency, Integrity and Transformation Quality.

===============

The mechanism is designed to meet confidentiality and privacy requirements. Customer bank-account details constitute sensitive financial information. Inspecting outgoing email for such values is a form of Data Loss Prevention control intended to identify or prevent inappropriate disclosure before sensitive information leaves the organization's controlled environment.

DAMA-DMBOK2 treats confidentiality and privacy as fundamental Data Security requirements. Its electronic-communication guidance warns that restricted or confidential information should not be sent through insecure communication channels because messages can be intercepted, forwarded, or otherwise disclosed after leaving the sender's control. DAMA International's own privacy practices likewise classify bank-account and similar financial information as protected personal/financial data requiring security safeguards against unauthorized disclosure.

The other responses concern transparency, definitions, user experience, or availability and do not address the security objective demonstrated in the scenario.

Data Governance determines the classifications and policies governing such information; Metadata Management can record sensitivity classifications against physical data elements; and security technology then enforces the resulting controls.

Data Quality remains relevant because confidentiality controls must distinguish genuinely sensitive values accurately. Poor classification or inaccurate detection rules may either expose protected information or unnecessarily block legitimate communication.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Confidentiality and Privacy; Electronic Communication Security; Sensitive Data; Data Loss Prevention; Data Governance.

===============

A proliferation of independently implemented data warehouses, lakes, and poorly governed “data swamps” commonly indicates that the organization has emphasized technology acquisition over establishing an integrated, authoritative view of enterprise data. The issue is not the existence of multiple technologies by itself; distributed platforms can be justified by legitimate architectural requirements. The warning sign is uncontrolled duplication without clear authoritative sources, enterprise architecture, governance, lineage, and consistency controls.

DAMA-DMBOK2 treats Data Architecture as the mechanism for aligning data assets with enterprise strategy and reducing unnecessary fragmentation. A mature architecture identifies authoritative sources, data flows, integration patterns, shared definitions, and the required relationship between operational and analytical stores. The DAMA framework also emphasizes that technologies should support business and data-management objectives rather than dictate them.

From a Data Quality perspective, uncontrolled proliferation creates competing versions of values, inconsistent transformations, duplicate master records, contradictory metrics, and unclear ownership. These conditions undermine consistency and make root-cause analysis difficult.

A “single point of truth” does not necessarily require one physical database. It requires controlled authority and consistent semantics across the landscape.

Reference Topics: DAMA-DMBOK2 — Data Architecture; Data as an Asset; Authoritative Sources; Data Integration; Metadata; Data Quality Consistency.

===============