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

Discovering and documenting metadata about physical data assets provides visibility into how data moves and is transformed between systems. This is a core function of technical metadata and data lineage.

DAMA-DMBOK2 states that technical metadata describes the technical characteristics of data, the systems that store it, and the processes that move it within and between systems. Examples include physical table and column names, ETL job information, source-to-target mappings, and lineage documentation with upstream and downstream impact information. The certification question therefore points directly to option D; the same interpretation is independently reflected in published CDMP-oriented material.

This capability is critical to Data Quality because a defect observed in a report or downstream application may not originate in the current system. It may have been introduced through extraction logic, transformation rules, reference-data conversion, aggregation, or loading.

Documented physical metadata allows analysts to trace the affected value backward, identify its source, inspect each transformation, and isolate the point at which the defect occurred. It also supports change-impact analysis: modifying a source field or mapping can reveal which downstream assets may be affected.

Metadata therefore provides the evidence required for systematic root-cause analysis rather than symptom-based correction.

Reference Topics: DAMA-DMBOK2 Metadata Management — Technical Metadata; Source-to-Target Mapping; Data Lineage; Data Integration and Interoperability; Chapter 13 — Root-Cause Analysis and Quality Monitoring.

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

The process is Encryption. DAMA-DMBOK2 defines encryption as converting readable plaintext into coded information so that privileged or sensitive content cannot be understood without the appropriate decryption mechanism. The DMBOK2 security section specifically describes encryption as translating plain text into complex codes to hide privileged information and also notes its use in protecting transmission integrity and validating identity.

Encryption supports confidentiality both at rest and in transit. Depending on implementation, organizations may use symmetric encryption, asymmetric or public-key encryption, hashing for particular integrity or authentication functions, and other cryptographic mechanisms.

The crucial distinction is that encryption deliberately changes the representation of information according to a cryptographic algorithm and key structure. Encapsulation, enhancement, elimination, and exaggeration are not substitutes for cryptographic protection.

Within the wider DAMA framework, encryption should be applied according to classification and risk. Highly sensitive information may require stronger cryptographic controls, restricted key management, rotation procedures, and separation of duties.

Data Quality and Data Security intersect at integrity: unauthorized changes may produce inaccurate data even when availability remains unaffected. Security controls therefore protect not merely secrecy but the reliability and trustworthiness of managed information.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Encryption; Confidentiality; Data Integrity; Cryptographic Controls; Security Classification.

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

The Party pattern generalizes Person and Organization under a common supertype so that both can participate consistently in shared business relationships and processes. The major benefit is that persons and organizations can act in roles in agreements, share address structures, and participate in common interaction processes, making option E correct.

For example, a Customer, Supplier, Account Holder, Employee, or Contracting Party may be either a person or an organization. Without the Party abstraction, separate relationships may need to be constructed repeatedly for Person and Organization. With Party, common concepts such as Agreement, Address, Contact Point, Role, and Interaction can reference a single generalized entity.

This is particularly relevant to Master Data Management because Party is a common enterprise modelling pattern for Customer, Supplier, and related master-data domains. It supports entity resolution while preserving distinctions between individuals and organizations through subtype structures.

From a Data Quality perspective, the approach improves consistency by reducing duplicated relationship definitions and business rules. However, governance must still establish subtype-specific requirements—for example, organization registration identifiers versus personal names and dates of birth.

The abstraction is therefore primarily about reusable semantic relationships and roles, not security concealment or faster package implementation.

Reference Topics: DAMA-DMBOK2 Chapter 5 — Data Modeling and Design; Generalization and Specialization; Party Model; Chapter 10 — Master Data; Chapter 13 — Consistency and Integrity.

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

The activity is Standardization. Standardization converts semantically equivalent values into a consistent representation so they can be compared, matched, integrated, and interpreted reliably.

In the scenario, Street, St., and Str may represent the same address concept but differ syntactically. Converting them to an approved standard reduces superficial variation before entity matching.

Standardization is commonly used for names, addresses, telephone numbers, units of measure, dates, product descriptions, geographic references, abbreviations, and coded values. It frequently precedes matching and de-duplication because entity-resolution algorithms perform more effectively when predictable representational differences have already been normalized.

Reference Data and Metadata Management are important supporting disciplines. Reference Data can define approved abbreviations or formats, while metadata documents transformation rules and intended meaning.

Standardization does not prove that the resulting address is factually accurate. It improves consistency and comparability. An address can be perfectly standardized yet belong to the wrong customer.

Therefore, standardization should be combined with validation, verification, matching, and source-improvement controls where appropriate.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Standardization; Cleansing; Matching; Consistency; Reference Data Management.

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

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.

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

Web-scale search-engine repositories commonly operate according to BASE: Basically Available, Soft State, Eventually Consistent. BASE is associated with distributed and many NoSQL data architectures where availability, horizontal scalability, and tolerance of distributed processing are prioritized over the immediate transactional consistency expected from traditional ACID systems.

A web crawler collects and indexes content continuously across very large distributed environments. Different nodes or indexes may temporarily contain slightly different versions of information while updates propagate. The design is acceptable because the system is expected to converge toward consistency rather than guarantee that every replica reflects the identical state at every instant. DAMA-aligned material explicitly contrasts BASE with traditional ACID approaches for large-scale distributed data processing.

ACID—Atomicity, Consistency, Isolation, Durability—is generally associated with transaction-oriented relational systems where individual transactions require strict integrity guarantees. Search indexing has different workload characteristics and can tolerate temporary inconsistency.

The Data Quality implication is that “consistency” must be evaluated according to architectural context. Temporary divergence can be expected behavior in an eventually consistent platform rather than evidence of a defect, provided convergence occurs within acceptable business thresholds.

Reference Topics: DAMA-DMBOK2 — Data Storage and Operations; Distributed Databases; NoSQL; ACID versus BASE; Availability; Consistency.

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