DQ-1220 DAMA Data Quality Specialist Free Practice Exam Questions (2026 Updated)

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.

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

This is Data Enrichment. Enrichment enhances existing records by adding useful information derived from internal or external sources. The original postal address remains intact, while geographic coordinates are appended to make the customer record more useful for location analysis, logistics, service coverage, route planning, or segmentation.

Enrichment differs from cleansing. Cleansing corrects or standardizes defective data; enrichment adds information that was not previously present. A process may perform both—for example, standardizing an address before passing it to a geocoding service.

External enrichment introduces governance and quality considerations. The organization should assess source reliability, licensing and permitted usage, refresh frequency, match confidence, geographical precision, lineage, and whether enrichment values should be treated as authoritative or derived.

Metadata should record that latitude and longitude were obtained from an external geocoding process rather than directly supplied by the customer. Quality metrics may measure match rate, confidence, completeness, or positional accuracy.

DAMA identifies Data Quality Management as including error detection, cleansing, and enrichment strategies, while Metadata Management supports understanding of lineage, definitions, and usage.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Data Enrichment; Cleansing; Profiling; Metadata Lineage; External Data Sources.

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

The conventional flow is Extract, Transform, and Load (ETL). Data is extracted from source systems, placed in a staging environment where required transformations are performed, and then loaded into the target Data Warehouse. Consequently, the transformed staging data is made ready and loaded into the Data Warehouse. DAMA-oriented training material presents this exact progression.

The staging area provides a controlled environment in which source data can be integrated without imposing transformation workloads directly on operational systems. Typical activities include datatype conversion, standardization, code translation, matching, deduplication, validation, derivation, consolidation, and handling rejected records.

From a Data Quality perspective, staging is especially important because many quality controls can be applied before data reaches the analytical repository. Profiling can identify unexpected distributions, invalid values, missing records, duplicate entities, referential-integrity defects, and inconsistent reference values. Failed records can then be quarantined or remediated according to governed rules.

Although metrics and profiling may occur in staging, they are supporting activities rather than the final destination in the ETL sequence. Likewise, metadata repositories document the transformation rather than serving as the main target for the transformed business data.

Reference Topics: DAMA-DMBOK2 — Data Warehousing and Business Intelligence; ETL; Staging Areas; Data Integration; Chapter 13 — Profiling, Cleansing, Standardization and Validation.

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

The primary issue is Uniqueness because more than one record represents the same real-world entity. Uniqueness evaluates whether unintended duplicate instances exist within a dataset or across integrated datasets.

Duplicate customer records can arise because of spelling variation, abbreviations, different contact details, weak matching rules, or inconsistent identifier capture. Exact duplicate detection alone is therefore insufficient. Effective entity resolution frequently requires probabilistic or deterministic matching across names, addresses, identifiers, telephone numbers, and other attributes.

DAMA-aligned Data Quality frameworks define uniqueness in terms of avoiding duplicate representation of the same entity. They also recognize that duplicate records may differ in individual attribute values while still representing the same person or object.

The issue is closely related to Master Data Management. An MDM process may match the three source records, establish that they belong to one customer, and apply survivorship rules to construct an authoritative master representation.

The correct remediation should also address the source process that allowed duplicates to be created; otherwise cleansing will merely remove symptoms while new duplicates continue to appear.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Uniqueness; Matching; De-duplication; Chapter 10 — Master Data Management; Entity Resolution.

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

Trend analysis is most useful because it shows how a quality metric changes over time rather than presenting a single isolated measurement.

A current defect rate of 4% has different implications depending on whether the previous months were 12%, 8%, and 6%, or 1%, 2%, and 3%. The first pattern indicates improvement; the second indicates deterioration.

Trend analysis therefore provides context for management decisions, helps determine whether remediation is producing sustained results, and can identify emerging degradation before thresholds are breached.

For stable, regularly measured processes, statistical control charts can add further value by distinguishing routine variation from signals that warrant investigation.

Metrics should be measured consistently over time. Changing definitions, populations, or calculation methods without documenting them can make apparent trends misleading.

Metadata should preserve metric definitions, threshold changes, and measurement logic to ensure comparability.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Monitoring; Trend Analysis; Statistical Control; Metrics; Continuous Improvement.

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

DAMA-DMBOK2 identifies capacity, availability, cache performance, and user statistics as representative metrics captured by database-monitoring tools. Database monitoring is an operational control mechanism used by Database Administrators and platform teams to understand whether database infrastructure is available, adequately sized, responsive, and being used as expected. DMBOK2 explicitly describes monitoring tools as automating the observation of metrics such as capacity, availability, cache performance, and user statistics.

Capacity metrics indicate resource consumption and future growth requirements. Availability measures whether data services remain accessible when required. Cache-performance measures help identify inefficient access patterns and bottlenecks, while user statistics provide information about workload and database consumption.

The other choices mix design concepts, CRUD operations, or Data Quality concepts with operational monitoring measures. For example, normalization is a modelling technique rather than a routine runtime performance metric. Similarly, “create, read, update, delete” describes basic data operations rather than monitoring indicators.

Although database performance and Data Quality are distinct disciplines, poor operational performance can affect Data Quality dimensions such as timeliness and availability. Monitoring therefore supports the technical environment in which governed, reliable information is delivered to users and applications.

Reference Topics: DAMA-DMBOK2 — Data Storage and Operations; Database Operations; Capacity and Availability Management; Monitoring; Chapter 13 — Timeliness and Operational Fitness for Purpose.

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

Remediation should principally be prioritized according to business impact and risk. Not all defects have equivalent consequences, even when they occur at similar frequencies.

A defect affecting regulatory reporting, customer payments, safety-critical operations, executive reporting, or high-value master data may require immediate remediation. A larger number of defects affecting a low-impact optional field may legitimately receive lower priority.

A robust prioritization model may consider financial loss, regulatory exposure, operational disruption, customer impact, reputational damage, number of dependent systems, recurrence rate, remediation cost, and whether a Critical Data Element is involved.

This risk-based approach prevents Data Quality programs from becoming simple defect-count reduction exercises. The objective is not merely to maximize the number of corrected records but to improve fitness for purpose where poor data creates material consequences.

Governance should approve prioritization criteria and resolve conflicts where different business areas assign different importance to the same issue. Metadata and lineage provide evidence about downstream dependencies and affected processes.

DAMA's revision of Chapter 13 adds a clearer Critical Data Element concept and clarifies responsibility within the Data Quality Improvement Lifecycle, reinforcing risk-based prioritization.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Issue Prioritization; Business Impact; Critical Data Elements; Risk; Remediation.

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

The dataset can be complete while remaining inaccurate. Completeness measures whether the required records and values are present; Accuracy measures whether those values correctly represent reality.

If every customer has a telephone number, the field may achieve 100% completeness. However, if 8% of those numbers belong to other people, the values are inaccurate.

This distinction is one of the most important principles in Data Quality measurement. A populated field is not automatically trustworthy. Similarly, a syntactically valid value is not necessarily accurate.

DAMA-aligned guidance explicitly distinguishes these dimensions and notes that a complete dataset may still contain incorrect values.

The appropriate quality scorecard should therefore present completeness and accuracy separately rather than treating one as evidence of the other.

For high-risk customer contact processes, the business may define independent thresholds for both dimensions. Verification services, customer confirmation, authoritative sources, and exception handling may be needed to improve accuracy after basic completeness has already been achieved.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Completeness; Accuracy; Data Quality Dimensions; Metrics; Fitness for Purpose.

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

The failed control is principally Reasonableness. DAMA treats reasonableness as the extent to which data values or patterns conform to credible expectations. The current DMBOK2 revision recognizes Reasonableness among the standard Data Quality dimensions, alongside Accuracy, Validity, Completeness, Integrity, Uniqueness, Timeliness, Currency and Consistency.

A $100,000,000 residential electricity bill may be syntactically valid: the field may accept the number, the record may satisfy referential constraints, and the value may have arrived on time. Nevertheless, it is grossly inconsistent with the customer's historical pattern of approximately $300 per quarter. A reasonableness control would therefore compare the amount with expected ranges, historical consumption, statistical limits, peer-group distributions, or business thresholds and flag the value before billing.

This illustrates an important distinction from Accuracy. Accuracy asks whether the stored value correctly represents reality. Reasonableness asks whether the value is credible in context. The absurd magnitude itself is detectable without first obtaining an independently verified “true” bill value.

Practical controls include range checks, deviation-from-history rules, z-score/outlier detection, control limits, and exception thresholds. Such rules should be governed as metadata and owned by an appropriate Data Steward.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Data Quality Dimensions; Reasonableness; Measurement and Monitoring; Statistical Process Control; Data Quality Rules.

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

DAMA-DMBOK2 organizes Data Handling Ethics around three fundamental considerations: impact on people, potential for misuse, and the economic value of data. The text explains that data frequently represents individuals and is used in decisions that materially affect them; consequently, organizations have an ethical responsibility to ensure that data is reliable and appropriately managed. It also recognizes that data can be intentionally or unintentionally misused and that its economic value creates questions concerning ownership, access, rights, and permitted use.

These concepts directly intersect with Data Quality. Incorrect or misleading data may result in decisions that adversely affect customers, employees, patients, citizens, or other stakeholders. For that reason, accuracy, completeness, transparency, provenance, and appropriate interpretation are not merely technical characteristics—they can have ethical consequences.

Governance operationalizes these ethical principles through policies, decision rights, stewardship responsibilities, access rules, monitoring, and escalation procedures. Metadata Management supports transparency by documenting meaning, provenance, classification, and permitted use. Master Data Management also has an ethical dimension because consolidated person or customer records may create significant consequences when matching or identity-resolution errors occur.

Privacy and security are important controls, but they do not constitute DAMA's complete set of core ethical concepts.

Reference Topics: DAMA-DMBOK2 Chapter 2 — Data Handling Ethics; Impact on People; Potential for Misuse; Economic Value of Data; Chapter 13 — Accuracy, Reliability and Governance.

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

The critical wording is “possible, but incorrect values.” This describes values that satisfy basic syntactic or domain validation—they look like legitimate dates—but do not accurately represent the real-world attribute defined by the field.

If two systems contribute data and one maps marriage date into the birth-date field, the resulting values can be perfectly valid calendar dates while being semantically incorrect as birth dates. This is principally an Accuracy defect, because DAMA defines accuracy in terms of how correctly data represents the real-world object or event it is intended to describe. It may also expose a consistency and integration-mapping problem between source systems. DAMA's quality framework distinguishes accuracy from completeness: data can be populated and formally valid while still being factually wrong.

Missing values would primarily produce a Completeness defect rather than populated-but-incorrect values. Two correctly mapped systems would not inherently explain the problem. An offset or technical date representation could create transformation problems, but the scenario most directly illustrates semantic mis-mapping between data elements.

The appropriate remediation is therefore not simple cleansing alone. Metadata mappings, source-to-target specifications, lineage, business definitions, and integration rules should be corrected at the root cause.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Accuracy, Completeness and Consistency; Root-Cause Remediation; Data Profiling; Metadata Management; Data Integration and Interoperability.

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

The organization should determine the root cause and authoritative remediation point before multiple teams independently modify downstream copies.

If a defective value originates in a source system and is distributed to five downstream applications, correcting those five copies independently may provide temporary relief but leaves the upstream defect intact. The incorrect value may simply be redistributed again.

Lineage should be used to trace the defect through source systems, transformations, integration layers, Master Data hubs, warehouses, and reports. Once the origin is understood, governance can determine which system or process is authoritative and where correction should occur.

This approach minimizes inconsistent local fixes and reduces the risk that different teams apply incompatible interpretations of the same issue.

DAMA's Chapter 13 revision explicitly strengthens the relationship between Data Quality and Metadata Management, Reference/Master Data Management, Modeling, and Data Integration. Those connections are precisely what enable cross-system issue resolution.

Downstream correction may still be required after the authoritative source is fixed, but it should be coordinated.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Root-Cause Analysis; Issue Management; Metadata Lineage; Authoritative Sources; Data Integration.

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

DAMA-DMBOK2 assigns primary responsibility for business glossary content to Business Data Stewards. Business Data Stewards are typically subject-matter experts who understand how data is defined, created, interpreted, and consumed within their business domain. DMBOK2 explicitly states that Data Stewards are generally responsible for business glossary content and identifies Business Data Stewards as professionals who work with stakeholders to define and control data.

A business glossary is not simply a technical dictionary. It establishes agreed business terminology, definitions, synonyms, business rules, responsible stewards, and relationships between business concepts. This makes stewardship involvement essential because definitions must reflect operational and business meaning rather than merely database structures.

Data Architects may contribute candidate definitions and structural context from subject-area and conceptual models, but they do not generally own the business meaning. Business users provide valuable input, while Coordinating Data Stewards help reconcile definitions across domains, yet the normal accountability remains with Business Data Stewards.

This relationship is particularly important for Data Quality. Quality rules depend on unambiguous definitions of data elements. If “Customer,” “Active Account,” or “Order Date” has inconsistent meanings, measurements of completeness, accuracy, and validity cannot be consistently interpreted.

Reference Topics: DAMA-DMBOK2 Chapter 3 — Develop a Business Glossary; Business Data Stewardship; Metadata Management; Chapter 13 — Data Quality Rules and Business Definitions.

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

The primary issue is Data Integrity, specifically referential integrity. The Orders record references a Customer_ID that does not correspond to an existing Customer record, meaning the relationship defined by the data model has been violated.

Integrity concerns whether structural relationships and constraints among data elements remain valid. In relational environments, this commonly includes primary-key uniqueness, foreign-key relationships, mandatory relationships, and cardinality constraints.

A customer identifier could be syntactically valid and populated, yet still fail integrity because no corresponding parent entity exists. This illustrates why integrity is different from completeness or validity. The DMBOK2 dimension model explicitly associates integrity with unique identifiers, cardinality, and referential integrity concepts.

Remediation should determine why the orphan record occurred. Potential causes include incorrect load sequencing, deletion of the parent record, integration failure, transformation defects, or absence of database constraints.

Metadata and Data Modeling establish the expected relationship; Data Quality controls then measure whether operational data conforms to it.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Data Integrity; Referential Integrity; Chapter 5 — Relationships and Keys; Data Integration Controls.

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

Compound authorization groups allow access rights from multiple groups or roles to be combined so that an individual's effective permissions can be configured with greater precision. The user may inherit one set of privileges from an organizational role, another from a functional group, and additional permissions from a specialized operational responsibility. The resulting authorization can therefore be more granular than assigning every privilege individually.

DAMA's Data Security framework separates authentication—establishing identity—from authorization, which determines what an authenticated identity is permitted to access or perform. Group-based authorization is a practical mechanism for implementing those decisions. CDMP-oriented references for this specific item identify “precisely configure an individual's access to a system” as the intended answer.

The principle must nevertheless be governed carefully. Excessive overlapping group memberships can make effective permissions difficult to review and can create segregation-of-duties conflicts. Periodic access reviews, least-privilege design, role ownership, and audit trails are therefore necessary complementary controls.

Encryption addresses confidentiality of data in transit or storage and is unrelated to how permissions are assigned. Audit preparation may benefit from structured authorization, but it is not the principal purpose.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Authorization; Access Control; Least Privilege; Security Roles; Audit and Monitoring.

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