DAMA DQ-1220 - DAMA Data Quality Specialist

A Business Continuity Plan is fundamentally concerned with maintaining essential business operations when normal services are disrupted. Therefore, the correct response is that it outlines how the business will continue operating during an unplanned disruption.

Within the DAMA-DMBOK2 framework, continuity concerns interact particularly with Data Governance, Data Storage and Operations, Data Security, and operational metadata. The DMBOK2 index explicitly identifies Business Continuity Plans and associates them with operational resilience and recovery concepts. A continuity plan must address how critical processes, information assets, personnel, technology, dependencies, and recovery arrangements will sustain or restore required business capability. The established definition of a BCP likewise centers on continued operation during unplanned service disruption.

Option E is incomplete: identifying potential disruptions belongs to risk assessment and continuity planning, but merely listing disruptions does not explain how operations will continue. Options B and D concern communications rather than continuity itself.

From a Data Quality perspective, continuity controls also protect availability, timeliness, integrity, and reliability. Recovery arrangements must ensure that restored data is complete, current enough for business use, and reconciled against authoritative sources after disruption.

Reference Topics: DAMA-DMBOK2 — Data Governance; Data Storage and Operations; Business Continuity; Disaster Recovery; Backup and Recovery; Chapter 13 — Timeliness, Integrity and Fitness for Purpose.

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

The correct long-term response is to remove the root cause in the source or integration process. Repeated warehouse cleansing treats symptoms. If the defect is recreated every night, operational costs continue and downstream systems remain exposed until the cleansing process executes.

DAMA Data Quality practice emphasizes sustained improvement rather than repeated correction. The quality lifecycle therefore includes identifying defects, determining business impact, analyzing root causes, implementing corrective actions, and monitoring results. The current Chapter 13 revision specifically strengthens clarification of the Data Quality Improvement Lifecycle and responsibilities within it.

The underlying cause might be weak source validation, an incorrect source-to-target mapping, outdated Reference Data, transformation logic, or missing governance over postal-code rules.

Cleansing remains appropriate where historical data must be repaired or immediate downstream protection is required. However, preventive control should be introduced as close to the creation point as practical.

Metadata and lineage help trace the postal code through the data flow, while governance establishes who has authority to change the offending process.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Root-Cause Analysis; Remediation; Prevention; Cleansing; Data Integration and Lineage.

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

Pareto analysis is the appropriate technique because it identifies the relatively small number of causes responsible for a large proportion of observed problems.

The team should arrange defect categories in descending order by frequency or business impact and calculate their cumulative contribution. If four categories account for 78% of complaints, prioritizing those categories is likely to generate substantially greater benefit than spreading equal effort across all twenty.

The value of Pareto analysis in Data Quality is not that every problem follows an exact 80/20 relationship. Rather, it provides an evidence-based mechanism for focusing scarce remediation resources on the defect classes that generate the most significant outcomes.

Frequency should not be the only prioritization criterion. A rare defect could produce severe regulatory, safety, financial, or reputational consequences. Governance should therefore combine volume analysis with business impact and risk.

Once priority defects are selected, the team should perform root-cause analysis and introduce preventive controls instead of merely fixing individual records.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Statistical Quality Tools; Pareto Analysis; Issue Prioritization; Business Impact; Root-Cause Remediation.

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

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.

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

An MDM investment is justified when the business value obtained from centralized coordination of shared data exceeds the additional cost of managing and integrating another controlled representation of that data. This is the economic trade-off expressed by option C and is also the intended answer in published versions of this DAMA question.

DAMA-DMBOK2 positions Master Data Management as a mechanism for improving consistency and control over enterprise entities such as customers, products, suppliers, employees, and locations. Uncoordinated local copies create redundant maintenance, inconsistent definitions, duplicate records, reconciliation costs, and integration complexity. DAMA sources emphasize that controlling shared master and reference data reduces both cost and risk generated by inconsistencies between systems.

However, introducing an MDM repository also incurs costs: integration, stewardship, matching, survivorship logic, synchronization, governance, maintenance, and potentially another physical copy of shared information. The business case must therefore demonstrate that improved coordination, quality, reuse, reporting, and operational consistency outweigh those costs.

MDM does not require all contributing systems to be decommissioned, nor does it eliminate Reference Data Management. Similarly, “mining golden records” is not the fundamental economic basis for MDM.

Reference Topics: DAMA-DMBOK2 Chapter 10 — Master Data Management; Business Drivers; Shared Data; Central Coordination; Data Integration; Data Quality and Stewardship.

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

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.

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

The required capability is Metadata lineage and impact analysis. Changing a business definition can affect far more than the glossary entry itself. The organization needs to know which physical fields, transformation rules, ETL jobs, calculations, reports, dashboards, analytical models, and downstream datasets depend on the current definition.

Lineage shows where data originates and how it flows and transforms. Impact analysis follows those relationships forward to determine what will be affected by a proposed change.

This prevents a common Data Quality failure in which a definition changes in one area while downstream systems continue applying the old interpretation. The result can be technically correct calculations that are semantically inconsistent.

A governed change should therefore update the business glossary, transformation metadata, Data Quality rules, reporting definitions, and affected documentation in a coordinated manner. Appropriate Data Stewards and Data Owners should approve the new meaning and effective date.

DAMA's framework describes Metadata Management as enabling understanding through definitions, lineage, and usage across systems, while the revised Chapter 13 explicitly strengthens the Data Quality–Metadata relationship.

Reference Topics: DAMA-DMBOK2 — Metadata Management; Data Lineage; Impact Analysis; Business Glossary; Data Quality Consistency.

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

All of these is correct because DAMA-DMBOK2 defines criticality according to the business use and impact of the data rather than by a particular technical characteristic. Critical Data Elements are commonly associated with regulatory, financial, or management reporting; operational business needs; measurement of product quality and customer satisfaction; and strategic initiatives such as competitive differentiation. DAMA's revised Chapter 13 also explicitly adds and clarifies the concept of Critical Data Elements within the Data Quality framework.

The purpose of identifying critical data is prioritization. Organizations cannot apply identical levels of profiling, monitoring, stewardship, remediation, and control to every data element. Data whose failure could create substantial operational, financial, legal, regulatory, customer, or reputational impact receives greater management attention.

For example, values feeding regulatory reports require stringent accuracy and traceability; operational data may require high availability and timeliness; customer-satisfaction measures require reliable and consistent inputs; and strategically important data can affect competitive decisions. Current DAMA-aligned material confirms these same usage categories for Critical Data Elements.

Once Critical Data Elements are identified, they should be linked to business definitions, Data Owners and Stewards, quality dimensions, measurable rules, lineage, authoritative sources, thresholds, and issue-management processes.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Critical Data Elements; Business Drivers; Data Quality Requirements; Prioritization; Data Governance; Metadata Management.

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

Compound authorization groups allow access rights from multiple groups or roles to be combined so that an individual's effective permissions can be configured with greater precision. The user may inherit one set of privileges from an organizational role, another from a functional group, and additional permissions from a specialized operational responsibility. The resulting authorization can therefore be more granular than assigning every privilege individually.

DAMA's Data Security framework separates authentication—establishing identity—from authorization, which determines what an authenticated identity is permitted to access or perform. Group-based authorization is a practical mechanism for implementing those decisions. CDMP-oriented references for this specific item identify “precisely configure an individual's access to a system” as the intended answer.

The principle must nevertheless be governed carefully. Excessive overlapping group memberships can make effective permissions difficult to review and can create segregation-of-duties conflicts. Periodic access reviews, least-privilege design, role ownership, and audit trails are therefore necessary complementary controls.

Encryption addresses confidentiality of data in transit or storage and is unrelated to how permissions are assigned. Audit preparation may benefit from structured authorization, but it is not the principal purpose.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Authorization; Access Control; Least Privilege; Security Roles; Audit and Monitoring.

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

DAMA-DMBOK2 identifies capacity, availability, cache performance, and user statistics as representative metrics captured by database-monitoring tools. Database monitoring is an operational control mechanism used by Database Administrators and platform teams to understand whether database infrastructure is available, adequately sized, responsive, and being used as expected. DMBOK2 explicitly describes monitoring tools as automating the observation of metrics such as capacity, availability, cache performance, and user statistics.

Capacity metrics indicate resource consumption and future growth requirements. Availability measures whether data services remain accessible when required. Cache-performance measures help identify inefficient access patterns and bottlenecks, while user statistics provide information about workload and database consumption.

The other choices mix design concepts, CRUD operations, or Data Quality concepts with operational monitoring measures. For example, normalization is a modelling technique rather than a routine runtime performance metric. Similarly, “create, read, update, delete” describes basic data operations rather than monitoring indicators.

Although database performance and Data Quality are distinct disciplines, poor operational performance can affect Data Quality dimensions such as timeliness and availability. Monitoring therefore supports the technical environment in which governed, reliable information is delivered to users and applications.

Reference Topics: DAMA-DMBOK2 — Data Storage and Operations; Database Operations; Capacity and Availability Management; Monitoring; Chapter 13 — Timeliness and Operational Fitness for Purpose.

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