Pass the DAMA CDMP DQ-1220 Questions and answers with ExamsMirror

Within the DMBOK2 framing used by this certification material, the expanded characteristics are Volume, Velocity, Variety/Variability, Viscosity, Volatility, and Veracity. Option E is therefore the only choice that correctly contains the DAMA terms represented in the question. DMBOK-oriented study material explains that the original three Vs—Volume, Velocity, and Variety—were expanded to include Variability, Viscosity, Volatility, and Veracity in the broader characterization.

Volume concerns data quantity; Velocity concerns the rate of creation and processing; Variety/Variability concerns differing structures and changing representations; Viscosity describes difficulty in using or integrating the data; Volatility concerns how quickly usefulness or meaning changes; and Veracity addresses credibility and trustworthiness.

These characteristics have direct Data Quality implications. Increased variety creates semantic and structural consistency challenges. Velocity reduces the time available for traditional validation. Volatility affects currency and timeliness. Veracity is directly concerned with reliability.

DAMA's key point is that Big Data does not reduce the need for management discipline. Its scale and complexity increase the need for metadata, governance, automated profiling, lineage, and statistically driven quality controls.

Reference Topics: DAMA-DMBOK2 Big Data and Data Science — Big Data Characteristics; Volume; Velocity; Variety/Variability; Viscosity; Volatility; Veracity; Chapter 13 — Scalable Data 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.

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

DAMA-DMBOK2 distinguishes descriptive, structural, and administrative metadata when discussing metadata classifications used outside conventional IT contexts. Descriptive metadata identifies and describes a resource sufficiently to enable discovery and retrieval. DMBOK2 gives title, author, and subject as explicit examples of descriptive metadata.

A book's author, title, and subject therefore answer practical discovery questions: What is the resource? Who created it? What is it about? These attributes allow catalogues, repositories, search tools, and users to identify and retrieve the required resource.

Option A is principally structural metadata. DMBOK2 specifically identifies the number of pages and chapters as examples describing relationships within or among the components of a resource. Option D represents administrative metadata because version numbers and archive dates help manage the resource throughout its lifecycle.

The distinction is important to Data Quality because metadata itself must have appropriate completeness, consistency, currency, and accuracy. Incorrect descriptive metadata can make a valid data asset effectively undiscoverable or lead users to select an inappropriate source.

Metadata Management therefore supports Data Quality by giving data consumers reliable definitions, context, provenance, ownership, lineage, and usage information.

Reference Topics: DAMA-DMBOK2 Metadata Management — Descriptive Metadata; Structural Metadata; Administrative Metadata; Metadata Quality; Chapter 13 — Data Quality and Metadata Management.

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

Although Data Lakes and Data Warehouses have materially different architectures, both support the broader objective of making organizational data available for reporting, analysis, analytics, and decision support. Therefore, option B identifies their legitimate conceptual overlap.

A traditional Data Warehouse generally contains integrated, curated, structured data designed for repeatable Business Intelligence, reporting, and analytical workloads. A Data Lake typically retains larger volumes of raw or less-structured information and supports flexible processing, exploration, Data Science, and advanced analytics. Both can therefore participate in analytical data pipelines even though their approaches to schema, transformation, governance, and consumption differ.

They do not inherently duplicate every item of operational data. Nor must a Data Lake produce dimensional or star-schema models; that modeling approach is more closely associated with traditional warehouse implementations. Governance is required for both rather than being the defining difference between them.

From a Data Quality standpoint, warehouses typically apply substantial cleansing and conformity before consumption. Lakes may retain raw values and defer interpretation, which increases the importance of metadata, provenance, cataloging, profiling, and consumer awareness.

Reference Topics: DAMA-DMBOK2 — Data Warehousing and Business Intelligence; Big Data; Data Lakes; Analytical Data; Metadata; Chapter 13 — Data Preparation and Fitness for Purpose.

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

The primary failure is Accuracy. Accuracy concerns whether a stored value correctly represents the real-world entity, event, or fact it is intended to describe. The recorded date is syntactically acceptable and conforms to the expected datatype and format, so it may satisfy Validity while still being factually wrong.

This distinction is fundamental in Data Quality assessment. A validity rule can determine whether a value is structurally permissible—for example, whether a date conforms to an approved pattern or whether a month lies between 1 and 12. It cannot by itself prove that the date belongs to the correct person. Government guidance based on DAMA dimensions makes the same distinction: a value can be valid while remaining inaccurate.

The strongest accuracy control would compare the value with an authoritative or independently verified source. Metadata should document the authoritative source and lineage, while governance should assign responsibility for resolving discrepancies.

The scenario therefore demonstrates why Data Quality programs must avoid assuming that format compliance equals correctness.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Accuracy; Validity; Authoritative Sources; Data Quality Rules; Metadata Lineage.

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

This is two-factor authentication (2FA). Authentication factors are distinguished by the type of evidence used to verify identity. A username identifies the account but does not constitute a separate authentication factor. The password represents something the user knows, while the code generated or delivered through an authentication application represents something the user has. Because two different factor categories are involved, the mechanism is two-factor authentication.

DAMA-DMBOK2 discusses multiple-factor identification as a security control for systems containing sensitive information. Its examples include a code returned to a user's mobile device, possession of a hardware device, and biometric factors such as fingerprints or facial recognition. DMBOK2 specifically notes that two-factor identification makes unauthorized account access substantially more difficult.

Three-factor authentication would require a third independent category, typically something the user is, such as a biometric characteristic. The mere fact that a username, password, and code are entered does not create three factors because the username is an identifier rather than authentication evidence.

From a Data Quality perspective, strong authentication protects integrity by reducing the risk that unauthorized users alter governed data, quality rules, metadata, or master records.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Authentication; Multiple-Factor Identification; Authorization; Data Security; Data Integrity.

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

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 precise DAMA-DMBOK2 purpose of Data Governance is to ensure that data is managed properly according to policies and best practices. DMBOK2 distinguishes this governance purpose from the broader objective of Data Management, which is concerned with obtaining value from data throughout its lifecycle.

Governance establishes the authority and control framework within which operational data-management functions work. This includes strategy, policy, standards, accountability, stewardship, compliance, issue escalation, quality oversight, and decision rights. DMBOK2 specifically identifies governance responsibilities involving policies for metadata, access, security and quality; setting Data Quality and Data Architecture standards; and providing oversight and corrective action.

This distinction is critical for Data Quality. Data Quality Management performs activities such as profiling, measurement, root-cause analysis, cleansing and monitoring. Data Governance determines who has authority, which requirements are mandatory, what thresholds are acceptable, which issues require escalation, and who owns remediation decisions.

Metadata Management supports governance by recording authoritative definitions, lineage, ownership and quality rules. Master Data Management operationalizes governance for shared business entities and reference domains.

Options B, C and D describe legitimate aspects of wider Data Management, but they do not state the specific purpose assigned to Data Governance by DMBOK2.

Reference Topics: DAMA-DMBOK2 Chapter 3 — Introduction; Goals and Principles; Governance Oversight; Chapter 13 — Data Quality and Governance.

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

The correct principle is “Doing it right when no one is looking.” The statement captures the essential distinction between ethical behaviour and mere compliance. Ethical conduct does not depend on observation, enforcement, or the probability of being caught; it requires responsible action because the action itself is appropriate. The answer wording is presented directly in the PDF on page 4.

DAMA-DMBOK2 treats data ethics as an essential component of professional Data Management because organizations routinely make choices about collecting, combining, analyzing, retaining, sharing, and monetizing data. A technically permissible activity may still create inappropriate effects on individuals or expose data to potential misuse.

Data ethics therefore extends beyond security and regulatory compliance. It requires consideration of the impact on people, potential for misuse, and economic value of data. Ethical handling also requires transparency concerning data provenance, intended use, quality limitations, and the consequences of decisions based on data.

Data Quality has an ethical dimension as well. Knowingly using inaccurate, incomplete, misleading, or poorly understood data in consequential decisions can harm customers and other stakeholders. Governance should therefore establish not only compliance controls but also principles for responsible use.

Reference Topics: DAMA-DMBOK2 Chapter 2 — Data Handling Ethics; Ethical Principles; Impact on People; Potential for Misuse; Chapter 13 — Reliable and Fit-for-Purpose Data.

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

A point materially outside established control limits is a classic signal of special-cause variation. Statistical Process Control distinguishes routine variation inherent in a stable process from unusual variation introduced by an identifiable event or change.

When a Data Quality process normally produces a stable percentage of invalid records and a sudden observation lies beyond the expected statistical range, investigation should focus on what changed. Possible causes include a new source system, software deployment, changed mapping, revised business rule, unusual batch, or manual processing error.

The current DMBOK2 Chapter 13 revision retains Statistical Process Control concepts while reorganizing them into supporting material and explicitly maps Shewhart/Deming improvement stages to Data Quality processes.

The signal does not prove what caused the defect, nor does it establish that performance has improved or deteriorated permanently. It indicates that the observed variation is sufficiently unusual to justify analysis.

Quality teams should preserve the evidence, correlate the timing with system and process changes, use lineage to identify affected sources, and investigate before adjusting the process unnecessarily.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Statistical Process Control; Control Charts; Common Cause; Special Cause; Continuous Improvement.

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