DQ-1220 Exam Dumps - DAMA Data Quality Specialist

GARP stands for Generally Accepted Recordkeeping Principles. ARMA International developed the framework to describe the characteristics of an effective records and information-management program. The principles address accountability, transparency, integrity, protection, compliance, availability, retention, and disposition.

These principles align closely with DAMA-DMBOK2's treatment of Document and Content Management. Information must be created, organized, protected, maintained, retrieved, retained, and ultimately disposed of according to business, legal, regulatory, and historical requirements. Records management is therefore not simply about long-term storage. It establishes controls throughout the information lifecycle.

For example, the Integrity principle addresses the authenticity and reliability of records. Availability requires information to be retrievable accurately and efficiently. Retention requires organizations to keep records for justified periods, while Disposition governs appropriate final handling after those obligations expire.

These controls interact directly with Data Quality. Records that cannot be found, trusted, interpreted, or demonstrated to be authentic are not fit for their intended purpose even if they physically exist.

Metadata Management supplies classification, retention, provenance, ownership, and lifecycle metadata necessary to implement these principles consistently.

Reference Topics: DAMA-DMBOK2 — Document and Content Management; Records Management; GARP; Retention; Disposition; Integrity; Metadata Management.

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

A Data Lineage tool provides the capture and maintenance of source structures for each attribute on the data model. Lineage connects modeled data elements to their originating structures and records how those elements move and transform through downstream systems. DAMA-related practice material identifies this specific capability as the correct function of lineage tooling.

At attribute level, lineage may identify a source table and column, transformation logic, staging structures, intermediate mappings, target columns, and ultimately the report or analytical object in which the value appears. This information allows organizations to answer fundamental questions such as: Where did this value originate? What transformations were applied? Which systems depend on this field? What downstream assets will be affected if its definition changes?

For Data Quality, lineage is a critical diagnostic capability. If a value becomes inaccurate after a transformation, lineage helps isolate the point of failure and distinguish source-system defects from integration or reporting defects. It also supports impact analysis before quality-rule changes are deployed.

Metadata Management normally provides the repository and technical structures that preserve lineage. Governance establishes ownership and documentation standards, while Data Stewards use lineage to understand business impact and coordinate remediation.

The other choices do not describe recognized lineage functions.

Reference Topics: DAMA-DMBOK2 — Metadata Management; Data Lineage; Data Architecture; Source-to-Target Mapping; Chapter 13 — Issue Investigation and Root-Cause Analysis.

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

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.

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

A business-data-driven roadmap translates the desired enterprise data architecture into an executable sequence of initiatives. DAMA-DMBOK2 explains that business capabilities consume and produce data, which creates dependencies between capabilities. The roadmap begins with relatively independent capabilities and progresses toward capabilities whose execution depends on data generated elsewhere. The architecture therefore establishes a coherent dependency chain before implementation work is organized.

The decisive final planning action is to turn that dependency sequence into implementable projects. Consequently, establishing the sequence of projects that will establish the data value chain is the best answer. Describing the data value chain, analysing data flows, identifying dependency challenges, and resequencing capabilities are analytical steps that precede portfolio sequencing.

DMBOK2 states that the roadmap should move from capabilities with the least dependency toward those with progressively greater dependencies, thereby providing the implementation order. It also emphasizes integrating the Enterprise Data Architecture roadmap with enterprise milestones, resources, and business-capability workstreams.

From a Data Quality perspective, sequencing matters because upstream master and reference data must reach an acceptable quality state before downstream transactional processes can depend on it.

Reference Topics: DAMA-DMBOK2 Chapter 4 — Data Architecture; Develop a Roadmap; Data Dependencies; Data Value Chain; Chapter 13 — Data Quality and other Knowledge Areas.

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

Periodic archiving is critical for maintaining database performance. As a production CRM accumulates historical transactions, active tables and indexes can become increasingly large. This increases storage consumption, backup duration, index-maintenance overhead, and the quantity of data that database engines must process during operational queries.

DAMA-DMBOK2 treats archiving as an important Data Storage and Operations activity. Historical information that remains subject to retention requirements but is no longer frequently needed for operational processing can be moved to suitable archival storage. DAMA-aligned guidance for this scenario specifically links periodic transaction archiving with maintaining production database performance.

Archiving is not the same as arbitrary deletion. Retention policies, legal obligations, recovery requirements, auditability, and business value determine how long data must remain accessible and where it should be stored. The archive must also be recoverable and appropriately secured.

Data Quality implications include maintaining integrity and traceability during migration to the archive. Records should remain complete, relationships should be preserved, and metadata should indicate retention status and archival location.

Providing reporting sources or managing deleted customers may be secondary considerations, but neither is the principal purpose described in the question.

Reference Topics: DAMA-DMBOK2 Chapter 6 — Data Storage and Operations; Archiving; Database Performance; Retention; Chapter 13 — Integrity and Historical Data.

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

DAMA-DMBOK2 defines Data Governance as the exercise of authority and control over the management of data assets. This definition distinguishes governance from the operational execution of Data Management. Independent literature describing DAMA's framework uses the same core formulation, and the DAMA Wheel places Data Governance across the other knowledge areas through this authority-and-control function.

Governance establishes decision rights, accountability, policies, standards, stewardship, issue escalation, compliance expectations, and mechanisms for monitoring whether data is being managed appropriately. It determines who is authorized to make decisions and what rules must be followed; individual Data Management knowledge areas then execute the corresponding operational activities.

Option E is closer to the broad definition of Data Management, because it refers to planning, implementation, and control across the information lifecycle. Option A describes an assessment or maturity activity. Option B describes selected governance benefits rather than its definition, while option C characterizes a collection of functions.

For Data Quality, governance provides the authority needed to define critical data, approve quality requirements and thresholds, assign accountability, prioritize remediation, and enforce standards. Without this authority structure, profiling may identify defects but the organization may lack the decision mechanisms required to correct their underlying causes.

Reference Topics: DAMA-DMBOK2 Chapter 3 — Data Governance Definition; Authority and Control; Policies and Standards; Chapter 13 — Data Quality Governance.

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

The correct long-term response is to remove the root cause in the source or integration process. Repeated warehouse cleansing treats symptoms. If the defect is recreated every night, operational costs continue and downstream systems remain exposed until the cleansing process executes.

DAMA Data Quality practice emphasizes sustained improvement rather than repeated correction. The quality lifecycle therefore includes identifying defects, determining business impact, analyzing root causes, implementing corrective actions, and monitoring results. The current Chapter 13 revision specifically strengthens clarification of the Data Quality Improvement Lifecycle and responsibilities within it.

The underlying cause might be weak source validation, an incorrect source-to-target mapping, outdated Reference Data, transformation logic, or missing governance over postal-code rules.

Cleansing remains appropriate where historical data must be repaired or immediate downstream protection is required. However, preventive control should be introduced as close to the creation point as practical.

Metadata and lineage help trace the postal code through the data flow, while governance establishes who has authority to change the offending process.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Root-Cause Analysis; Remediation; Prevention; Cleansing; Data Integration and Lineage.

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

Document and Content Management focuses on information stored outside conventional relational databases, including documents, images, multimedia, email, and other semi-structured or unstructured assets. Integrating this knowledge area with Data Security therefore guides the implementation of appropriate access and authorization controls for unstructured data.

DAMA's framework treats security as a cross-cutting discipline rather than something applicable only to database tables. Organizational documents can contain personally identifiable information, intellectual property, contracts, financial records, or other confidential material and therefore require the same disciplined approach to authentication, authorization, classification, retention, and monitoring as structured data. DAMA-aligned references explicitly identify appropriate access and authorization to unstructured data as the relevant interaction between these knowledge areas.

Metadata is also important because document classifications, ownership, retention category, confidentiality level, and permitted audiences provide the information needed to enforce controls.

Option A refers to structured data and therefore misses the specific contribution of Document and Content Management. Fitness-for-purpose measurement belongs primarily to Data Quality, while data-mart privacy addresses a narrower structured analytical environment.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Data Security; Chapter 9 — Document and Content Management; Unstructured Data; Access Control; Authorization; Information Classification.

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