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

The process is Survivorship. In Master Data Management, survivorship determines which value should become the preferred or authoritative representation when multiple source records contain conflicting values for the same attribute.

Rules may prioritize particular systems, use recency, trust scores, verification status, completeness, or combinations of factors. For example, a verified customer-service update might outrank an older marketing-system telephone number.

Survivorship occurs after or in conjunction with matching and entity resolution. The organization first determines that records from different sources represent the same real-world customer and then determines which attribute values should populate the mastered representation.

The process requires governance because the "best" value is a business decision, not merely a technical one. Data Stewards should approve the rules, and metadata should record source priority, rule logic, and lineage.

DAMA's framework positions Reference and Master Data Management as the discipline responsible for ensuring consistent core entities across the organization.

Reference Topics: DAMA-DMBOK2 Chapter 10 — Master Data Management; Matching; Survivorship; Authoritative Values; Chapter 13 — Consistency and Accuracy.

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

DAMA-DMBOK2 defines obfuscation or redaction as making information anonymous or removing sensitive information. The purpose is to reduce the risk that protected, confidential, or personally identifiable information can be exposed to users or processes that do not require access to the original values.

Obfuscation can involve masking, substitution, shuffling, temporal variation, partial display, or other methods that change what the recipient sees while preserving sufficient utility for the intended activity. For example, a customer-service agent may see only the final digits of an account identifier, or a development team may receive realistic but anonymized production-derived test data.

Redaction may remove information entirely from a representation when there is no legitimate requirement to expose it.

The technique is therefore a Data Security and privacy control, not database compression, publication, or classification.

There is also an important Data Quality consideration. Masked or obfuscated data used for testing must remain structurally valid and retain required relationships so that applications behave realistically. Metadata should indicate that a dataset has been transformed for privacy purposes so consumers do not mistake masked values for authoritative production data.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Obfuscation; Redaction; Data Masking; Privacy; Sensitive Information; Chapter 13 — Fitness for Purpose and Controlled Transformation.

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

Loading standardized country codes into a CRM is a classic example of Reference Data Integration. Country codes constitute controlled reference values used to classify or characterize other data. They differ from transactional information such as orders and payments and from master entities such as individual customers or products.

DAMA treats countries, currencies, geographic classifications, status codes, and similar controlled domains as typical Reference Data. The uploaded question therefore tests the distinction between integrating reusable code sets and integrating Master or Transaction Data. Published versions of the same DAMA item confirm Reference Data Integration as the intended answer.

In practice, an authoritative reference source may provide standardized country identifiers to CRM, ERP, MDM, analytical, and integration systems. Central management prevents different applications from independently inventing or changing equivalent codes.

This is also a Data Quality control. Reference integration improves Validity by restricting values to approved domains and Consistency by ensuring that different systems interpret equivalent countries identically. For example, an uncontrolled mixture of GB, UK, 826, and proprietary internal codes may create integration and reporting errors unless mappings are formally governed.

Metadata should document the authoritative source, code meaning, effective dates, mappings, ownership, and applicable standards.

Reference Topics: DAMA-DMBOK2 Chapter 10 — Reference Data; Code Sets; Reference Data Integration; Authoritative Sources; Chapter 13 — Validity and Consistency.

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

A high percentage of returned mail is primarily a Data Quality problem. Returned correspondence frequently results from inaccurate, incomplete, obsolete, incorrectly formatted, or otherwise unusable address data. The operational symptom therefore indicates that address information is failing to meet its intended business purpose.

Published versions of this DAMA question identify Data Quality as the intended knowledge area. The underlying principle aligns directly with DMBOK2 Chapter 13: quality is assessed relative to the requirements of the business process consuming the data.

Several quality dimensions may contribute. Accuracy concerns whether the address correctly represents the customer's actual location. Completeness concerns missing apartment numbers, postal codes, or address components. Validity evaluates whether values conform to accepted formats and domains. Currency addresses whether a previously correct address has become obsolete. Consistency can also be involved where address information differs between systems.

Reference and Master Data Management may provide customer-master consolidation and standardized geographic reference values, but the direct defect represented by returned mail is poor-quality address data.

A mature response should involve profiling returned-mail records, determining defect patterns and root causes, establishing address-quality rules, correcting affected records, and introducing preventive validation at capture.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Fitness for Purpose; Accuracy; Completeness; Validity; Currency; Profiling; Root-Cause Analysis.

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

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.

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

An emergency contact phone number belongs to the Employee master-data domain. Employee Master Data describes relatively stable information about employees that needs to be consistently identified and reused across organizational processes and systems. Contact details associated with an employee—including emergency-contact information—therefore fall naturally within an Employee MDM program rather than Product or Asset MDM.

The broader DAMA Master Data framework identifies employees as one of the recurring enterprise entities that may require coordinated management alongside customers, products, suppliers, locations, and similar core subjects. Published versions of this specific DAMA certification item likewise identify Employee as the correct domain.

Managing this information centrally or through coordinated master-data processes helps prevent conflicting phone numbers, obsolete emergency contacts, duplicate employee identities, and inconsistent values across Human Resources and other authorized systems.

The data is also sensitive personal information. Governance should therefore define ownership, access rights, retention rules, and permitted usage. Quality controls should address completeness, validity, currency, and accuracy, because outdated emergency-contact information may fail precisely when it is needed.

Metadata Management should record definitions and classifications so that “emergency contact phone number” is consistently distinguished from an employee's own mobile or work telephone number.

Reference Topics: DAMA-DMBOK2 Chapter 10 — Master Data Domains; Employee Master Data; Data Governance; Chapter 13 — Accuracy, Completeness and Currency.

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

The process is Survivorship. After records have been matched and determined to represent the same entity, survivorship rules determine which attribute values should populate the mastered or preferred representation.

For example, the organization may select the most recently verified telephone number, prioritize a government-verified legal name, or prefer addresses originating from a designated Customer Relationship Management system. Different attributes can use different survivorship rules.

Survivorship is not simply "choose the newest value." The appropriate method may consider source trust, verification status, recency, completeness, confidence scores, stewardship decisions, or combinations of these factors.

The rules must be governed because they determine what the organization subsequently treats as trusted master data. Metadata should record the rule, selected source, lineage, and effective date so the mastered record remains explainable.

DAMA identifies Reference and Master Data Management as responsible for maintaining consistency in core entities such as customers, products, and locations and for supporting trusted shared information.

The Data Quality dimensions involved commonly include Accuracy, Consistency, Currency, Completeness, and Uniqueness.

Reference Topics: DAMA-DMBOK2 Chapter 10 — Master Data Management; Matching; Survivorship; Golden Record; Chapter 13 — Consistency and Accuracy.

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

Effective security risk reduction begins by understanding what data exists, how sensitive or critical it is, and where it resides. A classification model provides this foundation by classifying data concepts according to protection requirements and linking those concepts to their physical implementations. The certification material reflects this DAMA principle directly.

Data cannot be protected proportionately if the organization does not know whether it represents public information, internal operational information, personally identifiable information, financial data, intellectual property, regulated information, or another sensitive category. Classification allows the organization to apply appropriate controls according to risk rather than treating every data asset identically.

Once classification is established, security teams can define access requirements, encryption needs, monitoring, retention controls, masking, authorization policies, and other safeguards. Metadata is essential because classifications must ultimately be connected to actual databases, files, attributes, interfaces, and repositories.

A firewall alone does not provide data-level protection, and role classification by itself addresses only one dimension of security. Similarly, an Enterprise Data Model describes organizational data structures but does not replace security classification.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Data Security; Data Classification; Risk Reduction; Sensitive Data Discovery; Metadata Management; Chapter 13 — Integrity and Controlled Use.

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

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 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.

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