Free DAMA DQ-1220 Practice Exam with Questions & Answers | Set: 4

The application change is a preventive Data Quality control because it prevents a known defect from being created in the first place.

A mandatory-field control ensures that records cannot be accepted without the required Product Identifier. This differs from a detective control, which would identify missing identifiers after records had already entered the system.

Preventive controls are generally preferable where the organization controls the point of data creation and the business rule is sufficiently clear. They reduce downstream cleansing, exception handling, reconciliation, and operational rework.

However, making the field technically mandatory is appropriate only if the business requirement genuinely applies to every relevant record. Governance and stewardship should confirm the rule before implementation. If certain product categories legitimately lack the identifier, the validation should incorporate those conditions instead of enforcing an overly broad requirement.

The Product Identifier may also link the transaction to governed Product Master Data, making integrity and consistency important alongside completeness.

DAMA's Data Quality framework emphasizes defining rules, detecting defects, implementing improvement, and integrating quality with Governance and Master Data disciplines rather than relying solely on after-the-fact cleansing.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Preventive Controls; Completeness; Data Quality Improvement Lifecycle; Chapter 10 — Product Master Data; Governance.

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

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

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

The 98.5% value is a measured Data Quality result, and because it is below the approved 99.5% threshold, it represents a threshold breach.

A Data Quality metric quantifies observed performance. A threshold establishes the level of performance the business has agreed is acceptable. These should not be confused. The metric answers how are we performing?; the threshold answers is that performance acceptable?

The 98.5% completeness result says nothing about whether the populated email addresses are accurate. A field can achieve high completeness while containing incorrect or invalid values. Other rules may therefore be required for email syntax, uniqueness, deliverability, or factual correctness.

A threshold breach should trigger a predefined response appropriate to the criticality of the data. This may involve investigation, escalation, remediation, trend review, or root-cause analysis.

Metrics, calculation logic, measurement population, thresholds, ownership, and escalation rules should be documented as metadata so dashboard results remain interpretable and reproducible.

DAMA's framework explicitly places metrics, error detection, cleansing, and quality management within Data Quality Management.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Data Quality Metrics; Thresholds; Scorecards; Completeness; Monitoring.

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

Each additional data item creates obligations across multiple lifecycle processes, which is why option D is the most complete answer. DAMA-DMBOK2 treats data as an asset that must be managed throughout an interconnected lifecycle rather than merely stored in a database. Activities include creation or acquisition, validation, integration, transformation, storage, maintenance, access, use, protection, retention, archiving, and disposal.

Consequently, introducing another meaningful data element may require changes to data models, metadata repositories, interfaces, mappings, business rules, validation controls, security classifications, quality measurements, lineage documentation, reporting logic, retention rules, and stewardship responsibilities. The cost is therefore cumulative across several management processes.

Option A identifies only migration. Option B reduces the impact to storage, which is usually a minor component. Option C applies only where a warehouse is involved. Option E identifies one legitimate consideration—security—but security is only one part of the complete management obligation.

The Data Quality implication is substantial. Every additional Critical Data Element may require explicit definitions of validity, completeness, accuracy, timeliness, and consistency, together with monitoring and issue-management procedures. This demonstrates why organizations should avoid collecting data indiscriminately and should manage data according to genuine business value and requirements.

Reference Topics: DAMA-DMBOK2 Chapter 1 — Data Lifecycle; Data as an Asset; Chapter 5 — Data Modeling; Chapter 13 — Data Quality Requirements and Monitoring.

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