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

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.

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

The scenario describes a many-to-many relationship: one Person may use several Addresses, while one Address may be associated with several Persons. In relational modelling, this should be resolved using an associative entity—here, Person Address Usage—between Person and Address. The original many-to-many relationship is thereby replaced with two one-to-many relationships. DAMA-oriented references identify this approach directly under the addition of associative entities.

The associative entity normally contains foreign keys referencing both parent entities and may also contain attributes describing the association itself, such as address type, usage purpose, effective date, end date, or primary-address indicator.

Simply modifying the primary keys of Person or Address does not resolve the semantic relationship. Changing foreign-key role names also changes terminology rather than cardinality. The term “partnership entity” is not the appropriate modelling construct.

This design has important Data Quality consequences. It permits explicit integrity constraints between the association and both parent entities, prevents ambiguous repeated columns, and allows the organization to validate rules such as valid effective periods and permitted address-use types.

Reference Topics: DAMA-DMBOK2 Chapter 5 — Relationships; Cardinality; Associative Entities; Resolving Many-to-Many Relationships; Chapter 13 — Referential Integrity and Consistency.

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

A strong Release Management process is critical when a Data Warehouse evolves incrementally. DAMA-DMBOK2 states directly that Release Management supports incremental development by coordinating new capabilities, enhancements, production deployment, and recurring maintenance of deployed warehouse assets.

A Data Warehouse is rarely completed in one implementation. Business requirements evolve, additional subject areas are onboarded, models are extended, transformation rules change, new reports are introduced, and defects are corrected. Release Management provides the controlled mechanism for packaging these changes into predictable production increments.

This requires prioritization of the backlog, coordination between business and technical teams, regression testing, deployment control, documentation, reconciliation, and validation of new or changed data structures. Without disciplined release management, incremental development can produce incompatible transformations, unstable reports, inconsistent historical treatment, and uncontrolled changes to definitions.

Data Quality should therefore form part of each release gate. New mappings and transformations should be profiled and reconciled; quality thresholds should be retested; metadata and lineage must be updated; and known exceptions should be documented.

Agile development may be used as a delivery method, but DAMA specifically identifies Release Management as the process critical to sustaining incremental warehouse evolution.

Reference Topics: DAMA-DMBOK2 Data Warehousing and Business Intelligence — Maintain Data Products; Release Management; Incremental Development; Chapter 13 — Quality Monitoring and Change Control.

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

A document-management search function depends heavily on metadata to identify, index, classify, and retrieve stored content. If known artefacts exist in the repository but cannot be found through search, inadequate or incorrectly maintained metadata is the most direct explanation.

DAMA-DMBOK2 distinguishes document content from the metadata that describes it. Typical descriptive metadata includes title, author, subject, keywords, document type, creation date, classification, and other characteristics used by retrieval mechanisms. Administrative and structural metadata may additionally support lifecycle management, versioning, access control, and relationships among document components. Without sufficiently accurate and complete metadata, the repository may physically contain a document while users remain unable to discover it.

This is also a Data Quality problem. Metadata itself is data and must satisfy quality expectations such as completeness, validity, consistency, and accuracy. A missing subject classification, incorrect document type, or inconsistent keyword convention can directly reduce findability.

Public access is neither required nor desirable for all documents, especially where confidential information exists. Business Intelligence is unrelated to basic document discovery, and Data Quality metrics alone do not make a document searchable unless the underlying metadata is correctly populated.

Reference Topics: DAMA-DMBOK2 — Document and Content Management; Metadata Management; Descriptive Metadata; Search and Retrieval; Chapter 13 — Metadata Quality and 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.

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

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.

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