DQ-1220 DAMA Data Quality Specialist Questions and Answers

The dataset can be complete while remaining inaccurate. Completeness measures whether the required records and values are present; Accuracy measures whether those values correctly represent reality.

If every customer has a telephone number, the field may achieve 100% completeness. However, if 8% of those numbers belong to other people, the values are inaccurate.

This distinction is one of the most important principles in Data Quality measurement. A populated field is not automatically trustworthy. Similarly, a syntactically valid value is not necessarily accurate.

DAMA-aligned guidance explicitly distinguishes these dimensions and notes that a complete dataset may still contain incorrect values.

The appropriate quality scorecard should therefore present completeness and accuracy separately rather than treating one as evidence of the other.

For high-risk customer contact processes, the business may define independent thresholds for both dimensions. Verification services, customer confirmation, authoritative sources, and exception handling may be needed to improve accuracy after basic completeness has already been achieved.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Completeness; Accuracy; Data Quality Dimensions; Metrics; Fitness for Purpose.

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

The DAMA-DMBOK2 Environmental Factors Hexagon illustrates the relationship between People, Process, and Technology. It provides a visual key for interpreting the Knowledge Area Context Diagrams and emphasizes that effective Data Management depends on the coordinated interaction of these three dimensions.

DMBOK2 places Goals and Principles at the center of the hexagon because they guide how people perform activities and how technology is selected and used. People-related factors include roles, responsibilities, organization, and culture. Process-related factors include activities, techniques, and methods. Technology-related factors include tools and the mechanisms that support Data Management deliverables.

This model is especially relevant to Data Quality. A profiling or cleansing platform alone cannot establish sustainable quality. The organization also needs accountable Data Owners and Data Stewards, repeatable issue-management and improvement processes, business-defined rules, and governance mechanisms. Conversely, well-designed processes will fail if supporting technologies cannot monitor or enforce required controls.

Option A relates more closely to the structure of DMBOK Knowledge Area Context Diagrams. The DAMA Wheel represents the Knowledge Areas, while the Environmental Factors Hexagon specifically emphasizes the People–Process–Technology relationship.

Reference Topics: DAMA-DMBOK2 Chapter 1 — DAMA-DMBOK Framework; Environmental Factors Hexagon; People, Process and Technology; Chapter 13 — Data Quality Organization, Processes and Tools.

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

The critical wording is “possible, but incorrect values.” This describes values that satisfy basic syntactic or domain validation—they look like legitimate dates—but do not accurately represent the real-world attribute defined by the field.

If two systems contribute data and one maps marriage date into the birth-date field, the resulting values can be perfectly valid calendar dates while being semantically incorrect as birth dates. This is principally an Accuracy defect, because DAMA defines accuracy in terms of how correctly data represents the real-world object or event it is intended to describe. It may also expose a consistency and integration-mapping problem between source systems. DAMA's quality framework distinguishes accuracy from completeness: data can be populated and formally valid while still being factually wrong.

Missing values would primarily produce a Completeness defect rather than populated-but-incorrect values. Two correctly mapped systems would not inherently explain the problem. An offset or technical date representation could create transformation problems, but the scenario most directly illustrates semantic mis-mapping between data elements.

The appropriate remediation is therefore not simple cleansing alone. Metadata mappings, source-to-target specifications, lineage, business definitions, and integration rules should be corrected at the root cause.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Accuracy, Completeness and Consistency; Root-Cause Remediation; Data Profiling; Metadata Management; Data Integration and Interoperability.

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

Country codes associated with country names are a classic example of Reference Data. DAMA-DMBOK2 defines Reference Data as data used to characterize or classify other data or to relate organizational data to externally defined information. The simplest reference-data structure consists of a code and its corresponding description. DMBOK2 specifically uses geographic and standards-based examples, including country codes such as DE, US, and TR.

A code such as GB therefore acts as a standardized machine-processable value, while “United Kingdom” supplies the human-readable meaning. Such code lists are reused across applications, integrations, reporting platforms, Master Data systems, and analytical environments.

Reference Data quality is important because inconsistent code sets can create widespread downstream defects. If different systems use incompatible country codes, the organization may experience failed integrations, incorrect aggregation, duplicate mappings, reporting discrepancies, and inconsistent interpretation. Data Governance should therefore establish authoritative sources and stewardship responsibilities for important reference domains.

Metadata Management records the meaning, provenance, permitted values, relationships, and mappings between code sets. Master Data Management frequently consumes these governed codes to classify master entities such as customers, suppliers, products, and locations.

The other choices describe relationships or transformations, but they do not represent the straightforward code-value/description list structure identified by DAMA.

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

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

The metric demonstrates Validity because it measures whether address values conform to a defined format or standard.

Validity checks whether data satisfies specified rules concerning datatype, pattern, permitted values, ranges, or structures. Postal formatting rules might require approved postcode structure, valid country-code syntax, or required address components.

The metric does not prove that the address belongs to the correct customer. A perfectly formatted address may still be factually wrong. That would be an Accuracy problem.

DAMA-aligned government guidance defines validity in terms of conformity to expected format, type, range, and other predefined rules.

A mature address-quality program may combine validity with verification against authoritative postal reference data, duplication checks, completeness rules, and currency monitoring.

Quality scorecards should therefore label the metric precisely rather than calling the result a generic "accuracy score."

Reference Topics: DAMA-DMBOK2 Chapter 13 — Validity; Accuracy; Data Quality Metrics; Address Quality; Reference Data.

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

The DAMA Wheel represents the principal Data Management Knowledge Areas defined by DAMA-DMBOK2. Data Governance occupies the central position because governance provides authority, coordination, standards, and oversight across the other disciplines. The surrounding areas include Data Architecture, Data Modeling and Design, Data Storage and Operations, Data Security, Data Integration and Interoperability, Document and Content Management, Reference and Master Data, Data Warehousing and Business Intelligence, Metadata Management, and Data Quality. DAMA descriptions of the framework identify these as Knowledge Areas rather than project deliverables or maturity dimensions.

The Wheel is deliberately integrative. No Data Management discipline operates effectively in complete isolation. For example, Data Quality relies on Governance for authority and accountability, Metadata Management for definitions and lineage, Reference and Master Data for consistent shared entities and codes, Data Architecture for structural context, and Integration for controlled movement between systems.

This interaction is central to Chapter 13. Data Quality cannot be reduced to cleansing defective records after problems appear. Sustainable quality requires coordinated management throughout the lifecycle and across the other DAMA knowledge areas.

Data management processes, deliverables, strategic initiatives, and maturity assessments are all legitimate DAMA concepts, but they are not what the DAMA Wheel itself principally represents.

Reference Topics: DAMA-DMBOK2 Chapter 1 — DAMA-DMBOK Framework; DAMA Wheel; Knowledge Areas; Chapter 3 — Governance; Chapter 13 — Data Quality Relationships with Other Knowledge Areas.

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

An effective Data Governance communication program should employ multiple complementary communication mechanisms, making All answers correct. Governance changes how people define, create, use, approve, and resolve issues with data; consequently, sustained adoption requires more than publishing policies.

Regular newsletters keep stakeholders aware of progress, decisions, metrics, and upcoming activities. A Data Governance Portal provides a persistent location for policies, standards, stewardship information, glossaries, issue processes, and supporting materials. Custom training develops the capabilities required for individuals to understand their specific governance responsibilities. Informal networking events help establish relationships across business and technical groups, which is particularly important when resolving data ownership and definition conflicts.

DAMA-DMBOK2 treats communication and organizational change as core implementation considerations because governance depends on participation across functions rather than on a single technical team. Published CDMP material for this item identifies the combined response—newsletters, portal, training, and networking—as the intended answer.

For Data Quality, communication ensures that quality definitions, issue-management procedures, stewardship responsibilities, thresholds, and remediation decisions are understood and consistently applied.

Reference Topics: DAMA-DMBOK2 Chapter 3 — Governance Communications; Organizational Change; Training; Data Governance Portal; Stewardship Engagement; Chapter 13 — Data Quality Culture.

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

Dimensions may be weighted differently because their business impact is not necessarily equal for a particular dataset or process.

For an emergency-response system, Timeliness may be more critical than completeness of optional descriptive fields. For regulatory reporting, Accuracy and Integrity may carry substantially greater risk than minor delays. For a marketing contact list, completeness and currency may dominate.

A composite Data Quality score should therefore reflect business priorities rather than assuming that each dimension contributes identical value. Weighting must be transparent and governed; otherwise a high score in low-impact dimensions could hide serious failure in a critical one.

The first step remains defining business requirements and Critical Data Elements. Once those are established, dimensions, thresholds, and weights can be linked to documented business consequences.

A score should also retain underlying component metrics. A single aggregate percentage is insufficient for diagnosis because two datasets with the same overall score may have very different risk profiles.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Metrics; Scorecards; Business Impact; Critical Data Elements; Quality Dimensions; Thresholds.

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

A Demilitarized Zone (DMZ) is a controlled network segment positioned between an organization's trusted internal environment and an external, untrusted environment such as the Internet. In the classic architecture described in DAMA-DMBOK2, the DMZ is separated from the Internet by an external firewall and from internal organizational systems by another firewall. Therefore, the correct answer is Internet and internal systems.

DMBOK2 describes the DMZ as an area on the organization's perimeter, with firewall protection separating it from the organization and firewall protection between the DMZ and the Internet. It is commonly used for services or transient data exchanges that must interact with external parties without providing direct access to internal systems.

This arrangement implements defense in depth. Public-facing services can operate in the DMZ while internal databases and sensitive systems remain behind an additional security boundary. A compromise of a DMZ host should therefore not automatically expose the internal network.

For Data Quality, security architecture is relevant because unauthorized modification or corruption can compromise integrity and accuracy. Protecting interfaces and repositories supports trustworthy data processing as well as confidentiality and availability.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Data Security; Network Security; Perimeter; DMZ; Firewalls; Integrity Protection.

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

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.

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

Data transformation includes operations such as format changes, structural changes, semantic conversion, de-duplication, and re-ordering. These activities modify source information so that it conforms to the syntactic, structural, or semantic requirements of a target environment.

A format transformation may convert dates from DD/MM/YYYY to an ISO representation. Structural transformation may split, combine, flatten, or restructure attributes. Semantic conversion changes representation while preserving intended meaning—for example, translating a source status code into the standardized enterprise code. De-duplication identifies multiple records representing the same real-world entity, while re-ordering changes the sequence or organization of records or attributes. The listed combination aligns directly with DAMA-oriented transformation guidance.

The distinction from the distractors is important. Organizational change, infrastructure replacement, or application modernization may trigger data transformation, but they are not themselves data-transformation techniques. “Re-duplication” is also inconsistent with the objective of improving integrated datasets.

Transformation is strongly connected to Data Quality. Poorly specified conversion rules can create invalid values, truncate data, introduce semantic inconsistencies, or produce duplicate entities. Consequently, transformations should be documented through mappings and metadata, tested against quality rules, reconciled with source totals, and monitored for exceptions.

Reference Topics: DAMA-DMBOK2 Chapter 8 — Transformation and Mapping; ETL/ELT; Chapter 13 — Standardization, Cleansing, De-duplication and Validation.

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

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.

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

The required capability is Data Lineage. Lineage documents how data originates, moves, transforms, and ultimately appears in downstream reports, applications, and analytical products.

When a report value is wrong, lineage allows investigators to trace the value backwards through calculations, mappings, staging structures, integration processes, source tables, and potentially external providers. This prevents teams from guessing where the defect originated.

Metadata Management is the principal discipline responsible for collecting and maintaining this contextual information. DAMA's public framework identifies lineage and definitions as central Metadata Management capabilities.

Lineage is also essential for change-impact analysis. If a source element changes, teams can determine which reports, models, or applications depend upon it.

For Data Quality, lineage supports root-cause analysis and coordinated remediation. A downstream value may be accurate relative to the transformation applied but still wrong because the source or transformation logic was incorrect.

Reference Topics: DAMA-DMBOK2 — Metadata Management; Data Lineage; Source-to-Target Mapping; Root-Cause Analysis; Data Integration.

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

The organization should continue monitoring the quality metric. A successful remediation does not guarantee that the underlying process will remain controlled indefinitely.

Systems change, source applications are upgraded, personnel and suppliers change, reference values evolve, interfaces are modified, and business rules are revised. Any of these events can cause previously corrected defects to reappear.

A mature Data Quality lifecycle therefore treats improvement as continuous rather than as a one-time cleansing exercise. DAMA's revision of Chapter 13 specifically clarifies the Data Quality Improvement Lifecycle and links it to established continuous-improvement cycles.

Monitoring should confirm that the result remains within agreed thresholds and should provide trend information so deterioration can be detected before it creates significant business impact.

The frequency of monitoring may be reduced after a process demonstrates sustained stability, but the decision should be risk-based. Critical Data Elements generally justify stronger ongoing oversight.

The rule, threshold, owner, and measurement method should remain documented as metadata.

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

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

Agile is not one of the four A's of Data Security. DAMA security guidance groups core security processes around Access, Audit, Authentication, and Authorization. These capabilities collectively control who can interact with information resources, establish identity, determine permitted actions, and provide evidence of activity for monitoring and accountability. DAMA-aligned security references identify these four concepts directly.

Authentication confirms the identity of a user or system. Authorization determines what an authenticated identity is permitted to do. Access concerns the actual ability to obtain or interact with data and services. Audit provides traceability by recording and reviewing relevant activities.

Agile, by contrast, is an approach to iterative delivery and project or product development. It may influence how security controls are implemented within development lifecycles, but it is not itself one of the foundational security-control categories identified in this model.

Data Security and Data Quality are separate but related disciplines. Unauthorized modifications can compromise accuracy and integrity, while weak auditability can prevent organizations from identifying how data was altered. Appropriate security controls therefore help preserve the reliability of governed information.

Metadata classification also supports these controls by identifying sensitive data and linking it to access and protection requirements.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Data Security; Access; Authentication; Authorization; Audit; Data Governance; Chapter 13 — Integrity and Controlled Data Modification.

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

This is Data Enrichment. Enrichment enhances existing records by adding useful information derived from internal or external sources. The original postal address remains intact, while geographic coordinates are appended to make the customer record more useful for location analysis, logistics, service coverage, route planning, or segmentation.

Enrichment differs from cleansing. Cleansing corrects or standardizes defective data; enrichment adds information that was not previously present. A process may perform both—for example, standardizing an address before passing it to a geocoding service.

External enrichment introduces governance and quality considerations. The organization should assess source reliability, licensing and permitted usage, refresh frequency, match confidence, geographical precision, lineage, and whether enrichment values should be treated as authoritative or derived.

Metadata should record that latitude and longitude were obtained from an external geocoding process rather than directly supplied by the customer. Quality metrics may measure match rate, confidence, completeness, or positional accuracy.

DAMA identifies Data Quality Management as including error detection, cleansing, and enrichment strategies, while Metadata Management supports understanding of lineage, definitions, and usage.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Data Enrichment; Cleansing; Profiling; Metadata Lineage; External Data Sources.

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

DAMA-DMBOK2 distinguishes descriptive, structural, and administrative metadata when discussing metadata classifications used outside conventional IT contexts. Descriptive metadata identifies and describes a resource sufficiently to enable discovery and retrieval. DMBOK2 gives title, author, and subject as explicit examples of descriptive metadata.

A book's author, title, and subject therefore answer practical discovery questions: What is the resource? Who created it? What is it about? These attributes allow catalogues, repositories, search tools, and users to identify and retrieve the required resource.

Option A is principally structural metadata. DMBOK2 specifically identifies the number of pages and chapters as examples describing relationships within or among the components of a resource. Option D represents administrative metadata because version numbers and archive dates help manage the resource throughout its lifecycle.

The distinction is important to Data Quality because metadata itself must have appropriate completeness, consistency, currency, and accuracy. Incorrect descriptive metadata can make a valid data asset effectively undiscoverable or lead users to select an inappropriate source.

Metadata Management therefore supports Data Quality by giving data consumers reliable definitions, context, provenance, ownership, lineage, and usage information.

Reference Topics: DAMA-DMBOK2 Metadata Management — Descriptive Metadata; Structural Metadata; Administrative Metadata; Metadata Quality; Chapter 13 — Data Quality and Metadata Management.

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

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.

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

A proliferation of independently implemented data warehouses, lakes, and poorly governed “data swamps” commonly indicates that the organization has emphasized technology acquisition over establishing an integrated, authoritative view of enterprise data. The issue is not the existence of multiple technologies by itself; distributed platforms can be justified by legitimate architectural requirements. The warning sign is uncontrolled duplication without clear authoritative sources, enterprise architecture, governance, lineage, and consistency controls.

DAMA-DMBOK2 treats Data Architecture as the mechanism for aligning data assets with enterprise strategy and reducing unnecessary fragmentation. A mature architecture identifies authoritative sources, data flows, integration patterns, shared definitions, and the required relationship between operational and analytical stores. The DAMA framework also emphasizes that technologies should support business and data-management objectives rather than dictate them.

From a Data Quality perspective, uncontrolled proliferation creates competing versions of values, inconsistent transformations, duplicate master records, contradictory metrics, and unclear ownership. These conditions undermine consistency and make root-cause analysis difficult.

A “single point of truth” does not necessarily require one physical database. It requires controlled authority and consistent semantics across the landscape.

Reference Topics: DAMA-DMBOK2 — Data Architecture; Data as an Asset; Authoritative Sources; Data Integration; Metadata; Data Quality Consistency.

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

The definition describes Data Policies. DAMA-DMBOK2 states that data policies are directives that translate organizational principles and management intent into fundamental rules controlling how data is created, acquired, protected, maintained, assured for quality, and used.

The distinction between governance and policy is important. Data Governance is the broader authority and decision-making framework. Policies are one of the principal instruments produced or sponsored through that framework. They define what must or must not occur. Standards and procedures subsequently translate those policies into specific implementation requirements and operational methods.

For Data Quality, a policy might require business-critical data to have designated ownership, documented definitions, measurable quality rules, monitored thresholds, and formal remediation processes. The detailed thresholds themselves may reside in standards or rule repositories rather than in the high-level policy.

Metadata Management makes policy operational by documenting definitions, classifications, ownership, lineage and applicable quality rules. Master Data Management applies those policies to shared business entities and controlled reference values. Data Stewards then monitor compliance and escalate violations through governance mechanisms.

Data asset valuation is concerned with determining economic value, while Data Management encompasses the complete discipline. Neither provides the specific “directive” definition stated in the question.

Reference Topics: DAMA-DMBOK2 Chapter 3 — Data Policies; Governance Principles; Standards and Procedures; Chapter 13 — Data Quality Governance; Metadata and Master Data interactions.

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

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.

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

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.

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

DAMA-DMBOK2 recommends an incremental implementation strategy for Data Governance because governance introduces changes in accountability, decision rights, standards, processes, and organizational behaviour. Attempting an enterprise-wide implementation immediately creates unnecessary cultural and operational risk.

The implementation guidance is explicit that most governance rollout strategies are incremental, commonly beginning with a significant initiative such as Master Data Management or with a particular region, business unit, or domain. Enterprise-wide deployment as the initial step is described as uncommon.

Incremental implementation provides several control advantages. The organization can validate roles and decision mechanisms, establish stewardship practices, prove business value, refine policies, develop metrics, and correct weaknesses before expanding the governance framework. This aligns closely with Data Quality management, where organizations normally prioritize Critical Data Elements and high-value domains rather than attempting to measure and remediate every data element simultaneously.

Executive sponsorship is important, but a mandate alone does not produce sustainable adoption. Likewise, individual leadership charisma cannot substitute for operating processes, accountability, metrics, and change management. A short consultant-driven exercise also conflicts with DAMA's treatment of governance as an ongoing organizational capability.

Incremental rollout therefore offers the strongest mechanism for embedding governance permanently while demonstrating measurable value.

Reference Topics: DAMA-DMBOK2 Chapter 3 — Implementation Guidelines; Organization and Culture; Adjustment and Communication; Chapter 13 — Data Quality Improvement and Governance.

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

The strongest indicator is the uncontrolled proliferation of multiple integration technologies. Enterprise integration environments often become progressively more complex when different projects independently adopt different ETL platforms, messaging products, APIs, middleware technologies, replication mechanisms, file-transfer approaches, and proprietary interfaces.

The problem is architectural fragmentation. Each integration technology introduces its own configuration methods, transformation logic, monitoring mechanisms, metadata, failure handling, security controls, support skills, and operational procedures. As the number of technologies increases, point-to-point dependencies multiply and the organization accumulates technical debt. This makes end-to-end lineage, troubleshooting, change-impact analysis, and consistent application of Data Quality rules significantly harder. The source question itself identifies this specific integration-management issue. DAMA-oriented exam material likewise identifies multiple integration technologies as the characteristic cause of an overly complex integration landscape.

DAMA-DMBOK2 therefore emphasizes managed Data Integration and Interoperability architecture, reusable patterns, common models, governed interfaces, and metadata describing transformations.

From a Data Quality perspective, uncontrolled integration technology can result in inconsistent transformations, duplicated cleansing rules, mismatched reference values, and poorly understood lineage. Standardization reduces these risks by making movement and transformation processes more transparent and governable.

Reference Topics: DAMA-DMBOK2 Chapter 8 — Data Integration and Interoperability; Integration Architecture; Metadata and Lineage; Chapter 13 — Quality Controls Across Data Movement.

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

The primary issue is Data Integrity, specifically referential integrity. The Orders record references a Customer_ID that does not correspond to an existing Customer record, meaning the relationship defined by the data model has been violated.

Integrity concerns whether structural relationships and constraints among data elements remain valid. In relational environments, this commonly includes primary-key uniqueness, foreign-key relationships, mandatory relationships, and cardinality constraints.

A customer identifier could be syntactically valid and populated, yet still fail integrity because no corresponding parent entity exists. This illustrates why integrity is different from completeness or validity. The DMBOK2 dimension model explicitly associates integrity with unique identifiers, cardinality, and referential integrity concepts.

Remediation should determine why the orphan record occurred. Potential causes include incorrect load sequencing, deletion of the parent record, integration failure, transformation defects, or absence of database constraints.

Metadata and Data Modeling establish the expected relationship; Data Quality controls then measure whether operational data conforms to it.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Data Integrity; Referential Integrity; Chapter 5 — Relationships and Keys; Data Integration Controls.

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

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.

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

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.

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

Integrated strategic reviews provide the strongest mechanism for managing a Data Architecture roadmap because the roadmap must remain synchronized with enterprise strategy, business capability priorities, other architecture domains, projects, resources, and changing dependencies.

DAMA-DMBOK2 describes the Enterprise Data Architecture roadmap as the three-to-five-year path by which the target architecture becomes reality. Crucially, it states that this roadmap must be integrated into the overall Enterprise Architecture roadmap, including milestones, required resources, cost estimates, and business-capability workstreams. The roadmap should also reflect business requirements, current conditions, technical assessments, and organizational maturity.

This means roadmap management cannot sensibly be reduced to a once-a-year exercise. Strategic conditions, technology decisions, project sequencing, dependencies, and regulatory requirements may change throughout the roadmap period. Integrated reviews allow those changes to be evaluated in the context of the wider enterprise architecture rather than independently.

Senior-management support is necessary for authority and funding, while peer reviews and results evaluation are useful control activities. None, however, provides the same integrated strategic mechanism for keeping architectural direction aligned with enterprise priorities.

From a Data Quality perspective, such reviews also ensure that architecture changes preserve authoritative sources, lineage, integration controls, and enterprise quality requirements.

Reference Topics: DAMA-DMBOK2 Chapter 4 — Develop a Roadmap; Enterprise Architecture Integration; Data Dependencies; Lifecycle Reviews; Architecture Governance.

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

The organization should determine the root cause and authoritative remediation point before multiple teams independently modify downstream copies.

If a defective value originates in a source system and is distributed to five downstream applications, correcting those five copies independently may provide temporary relief but leaves the upstream defect intact. The incorrect value may simply be redistributed again.

Lineage should be used to trace the defect through source systems, transformations, integration layers, Master Data hubs, warehouses, and reports. Once the origin is understood, governance can determine which system or process is authoritative and where correction should occur.

This approach minimizes inconsistent local fixes and reduces the risk that different teams apply incompatible interpretations of the same issue.

DAMA's Chapter 13 revision explicitly strengthens the relationship between Data Quality and Metadata Management, Reference/Master Data Management, Modeling, and Data Integration. Those connections are precisely what enable cross-system issue resolution.

Downstream correction may still be required after the authoritative source is fixed, but it should be coordinated.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Root-Cause Analysis; Issue Management; Metadata Lineage; Authoritative Sources; Data Integration.

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

The defect is measured using Completeness. Completeness evaluates whether all required records or values that should be present are actually present. In this scenario, the mandatory Tax Identification Number is absent from 2,500 of 50,000 customer records.

A straightforward attribute-level completeness metric would be calculated as the number of populated required values divided by the number expected. Therefore, 47,500 of 50,000 records contain the required value, producing a completeness result of 95%.

Completeness does not establish that populated values are accurate. A record may contain a Tax Identification Number and therefore pass the completeness rule while containing the wrong number. This separation between completeness and accuracy is essential when designing Data Quality scorecards. DAMA-aligned guidance defines completeness as the presence of required values and explicitly distinguishes it from factual correctness.

Governance should also determine whether the attribute is genuinely mandatory for every customer type. Quality rules must reflect business applicability rather than blindly requiring every field for every record.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Completeness; Data Quality Metrics; Business Rules; Critical Data Elements; Scorecards.

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

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.

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

This is Reference Data Management. Country codes represent a controlled set of values used to classify or contextualize other data. Managing them centrally helps ensure that all systems interpret the same codes consistently.

Without centralized governance, one system might use GB, another UK, and another proprietary numeric values. Those differences create mapping complexity, failed integrations, inaccurate aggregation, and inconsistent reporting.

Reference Data Management establishes authoritative sources, stewardship, allowed values, mappings, effective dates, distribution processes, and change control. DAMA's public framework describes Reference and Master Data Management as ensuring consistency in core shared information across organizational units.

The Data Quality dimensions most directly supported are Validity and Consistency. Validity ensures values belong to an approved domain; consistency ensures equivalent concepts are represented compatibly across systems.

Metadata should document the standard, meaning, owner, and version of each reference domain.

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

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

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.

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