Practice Free DQ-1220 DAMA Data Quality Specialist Exam Questions Answers With Explanation

The broad role of Metadata is to help organizations understand their data, systems, and workflows. Metadata provides the context required to interpret data correctly and connect business meaning with technical implementation and operational processing. This answer is also explicitly identified in DAMA-oriented certification material.

Business metadata explains concepts, definitions, rules, ownership, stewardship, and terminology. Technical metadata describes tables, columns, datatypes, interfaces, transformations, and system structures. Operational metadata captures information about processing, execution, schedules, and usage. Together, these categories explain what information means, where it resides, how it moves, and how it is used.

Metadata can certainly improve decision-making, support Big Data solutions, group concepts, and assist reporting, but those are secondary outcomes. Option C expresses its enterprise-wide role most comprehensively.

Its connection to Data Quality is fundamental. Quality cannot be assessed consistently without metadata explaining the intended meaning and acceptable characteristics of a data element. Lineage allows a defect to be traced to its origin, while business definitions establish the context for accuracy and validity measurements.

Reference Topics: DAMA-DMBOK2 Metadata Management — Business, Technical and Operational Metadata; Data Lineage; Business Glossary; Chapter 13 — Data Quality Rules and Metadata Dependencies.

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

Within the DMBOK2 framing used by this certification material, the expanded characteristics are Volume, Velocity, Variety/Variability, Viscosity, Volatility, and Veracity. Option E is therefore the only choice that correctly contains the DAMA terms represented in the question. DMBOK-oriented study material explains that the original three Vs—Volume, Velocity, and Variety—were expanded to include Variability, Viscosity, Volatility, and Veracity in the broader characterization.

Volume concerns data quantity; Velocity concerns the rate of creation and processing; Variety/Variability concerns differing structures and changing representations; Viscosity describes difficulty in using or integrating the data; Volatility concerns how quickly usefulness or meaning changes; and Veracity addresses credibility and trustworthiness.

These characteristics have direct Data Quality implications. Increased variety creates semantic and structural consistency challenges. Velocity reduces the time available for traditional validation. Volatility affects currency and timeliness. Veracity is directly concerned with reliability.

DAMA's key point is that Big Data does not reduce the need for management discipline. Its scale and complexity increase the need for metadata, governance, automated profiling, lineage, and statistically driven quality controls.

Reference Topics: DAMA-DMBOK2 Big Data and Data Science — Big Data Characteristics; Volume; Velocity; Variety/Variability; Viscosity; Volatility; Veracity; Chapter 13 — Scalable Data Quality.

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

The integration specification requires a documented transformation rule defining how pounds are converted to kilograms.

Source-to-target mappings should identify source attributes, target attributes, transformation logic, units, datatypes, validation expectations, and handling of exceptions. Without this metadata, different interfaces could apply different conversion factors or rounding rules and create inconsistent downstream values.

The rule should specify the approved conversion factor, precision, rounding method, treatment of nulls, and any acceptable source ranges. Testing should confirm that the transformed values remain within defined quality thresholds.

This illustrates the relationship between Data Integration, Metadata Management, and Data Quality that DAMA's current Chapter 13 revision makes more explicit.

The source value may be completely accurate in pounds while the target value becomes inaccurate through faulty transformation. Therefore, quality responsibility extends beyond original data capture.

Lineage should retain both the source and transformation information so downstream analysts can understand how the kilogram value was derived.

Reference Topics: DAMA-DMBOK2 — Data Integration and Interoperability; Source-to-Target Mapping; Transformation; Metadata Lineage; Accuracy.

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

Periodic archiving is critical for maintaining database performance. As a production CRM accumulates historical transactions, active tables and indexes can become increasingly large. This increases storage consumption, backup duration, index-maintenance overhead, and the quantity of data that database engines must process during operational queries.

DAMA-DMBOK2 treats archiving as an important Data Storage and Operations activity. Historical information that remains subject to retention requirements but is no longer frequently needed for operational processing can be moved to suitable archival storage. DAMA-aligned guidance for this scenario specifically links periodic transaction archiving with maintaining production database performance.

Archiving is not the same as arbitrary deletion. Retention policies, legal obligations, recovery requirements, auditability, and business value determine how long data must remain accessible and where it should be stored. The archive must also be recoverable and appropriately secured.

Data Quality implications include maintaining integrity and traceability during migration to the archive. Records should remain complete, relationships should be preserved, and metadata should indicate retention status and archival location.

Providing reporting sources or managing deleted customers may be secondary considerations, but neither is the principal purpose described in the question.

Reference Topics: DAMA-DMBOK2 Chapter 6 — Data Storage and Operations; Archiving; Database Performance; Retention; Chapter 13 — Integrity and Historical Data.

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

A process can be statistically stable yet still perform at an unacceptable quality level. Statistical control means that variation is predictable within the established process; it does not mean that the average level of defects satisfies business expectations.

For example, a process may consistently produce a 3% defect rate with very little month-to-month variation. If the business requirement is below 0.5%, the process is stable but incapable of meeting the desired quality level without improvement.

The appropriate response is therefore deliberate process improvement aimed at changing the underlying process and reducing its baseline defect rate. This differs from reacting to random individual observations within normal control limits.

After improvement, new performance data should be collected and control parameters reevaluated once the revised process reaches a stable state.

DAMA's revised Chapter 13 explicitly maps Shewhart and Deming improvement-cycle stages to Data Quality processes and preserves Statistical Process Control as supporting material.

The central principle is that control and capability are different questions: control asks whether the process is stable; business quality requirements determine whether that stable performance is good enough.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Statistical Process Control; Process Stability; Continuous Improvement; Shewhart/Deming Cycle; Thresholds.

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

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.

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

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.

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

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.

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

The concept described is Data Lineage. Data lineage records how data originates, moves, transforms, and is consumed across the information landscape. DAMA-oriented architecture guidance explicitly links implementation of Data Architecture with visibility into transformations occurring as data traverses systems and identifies this as lineage.

Lineage can operate at several levels. At a high level, it may identify that customer information moves from CRM into an integration platform, Master Data hub, warehouse, and reporting environment. At a detailed level, it may show that a particular report column derives from a specific source attribute through documented calculations, mappings, and transformation rules.

This capability is fundamental to Data Quality. When an incorrect result appears in a report, lineage helps analysts trace the defect upstream to the point where it originated or was introduced. It also supports root-cause analysis, impact assessment, regulatory traceability, change management, and reconciliation.

Metadata Management provides the repository structures needed to capture and maintain lineage. Data Governance determines which lineage must be documented and who is accountable for maintaining it.

ETL is one mechanism through which data may move and transform, but ETL is not the architectural concept describing the end-to-end history and derivation of the data.

Reference Topics: DAMA-DMBOK2 Chapter 4 — Data Architecture; Chapter 11 — Metadata Management; Data Lineage; Chapter 13 — Root-Cause Analysis and Data Quality Traceability.

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

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 issue is Currency. Currency concerns whether data remains sufficiently aligned with the current real-world state. The address was accurate when originally captured, but reality changed and the system was not updated.

This distinction matters because Data Quality can degrade over time without any technical error being introduced. Customer addresses, employment details, product prices, organizational structures, regulatory classifications, and contact details all have varying rates of change. A dataset that was reliable last year may no longer be fit for operational use today.

DAMA's current Chapter 13 revision explicitly identifies Currency as one of the nine standard Data Quality dimensions. Related DAMA-derived guidance also notes that real-world information changes and can therefore become outdated even when it was initially correct.

Organizations should establish refresh expectations according to business use. A marketing mailing list may tolerate a different update interval from an emergency-contact database.

Metadata should document refresh frequency and source authority, while quality monitoring can identify records exceeding acceptable age thresholds.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Currency; Accuracy; Timeliness; Data Aging; Monitoring; Fitness for Purpose.

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

The primary failure is Timeliness. The transaction may be completely accurate and complete, but it is not available within the period required by the consuming business process.

Timeliness evaluates whether data is available when needed for its intended use. The relevant threshold must therefore come from the business requirement rather than from an arbitrary technical target. In this scenario, the fraud-monitoring process requires the transaction within five minutes, while delivery occurs approximately nine hours later.

The root cause could exist in extraction frequency, integration queues, batch processing, network delays, source-system availability, or downstream ingestion. Lineage and operational metadata should be used to identify where the latency occurs.

Timeliness must also be distinguished from Currency. Currency asks whether information reflects a sufficiently recent real-world state; Timeliness asks whether data is delivered or available within the required period. A current transaction that arrives too late can therefore fail Timeliness even though the underlying value accurately represented reality when captured.

DAMA's revised DMBOK2 Chapter 13 recognizes both Timeliness and Currency as separate standard dimensions.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Timeliness; Currency; Data Quality Requirements; Data Integration; Operational Monitoring.

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

The mechanism is designed to meet confidentiality and privacy requirements. Customer bank-account details constitute sensitive financial information. Inspecting outgoing email for such values is a form of Data Loss Prevention control intended to identify or prevent inappropriate disclosure before sensitive information leaves the organization's controlled environment.

DAMA-DMBOK2 treats confidentiality and privacy as fundamental Data Security requirements. Its electronic-communication guidance warns that restricted or confidential information should not be sent through insecure communication channels because messages can be intercepted, forwarded, or otherwise disclosed after leaving the sender's control. DAMA International's own privacy practices likewise classify bank-account and similar financial information as protected personal/financial data requiring security safeguards against unauthorized disclosure.

The other responses concern transparency, definitions, user experience, or availability and do not address the security objective demonstrated in the scenario.

Data Governance determines the classifications and policies governing such information; Metadata Management can record sensitivity classifications against physical data elements; and security technology then enforces the resulting controls.

Data Quality remains relevant because confidentiality controls must distinguish genuinely sensitive values accurately. Poor classification or inaccurate detection rules may either expose protected information or unnecessarily block legitimate communication.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Confidentiality and Privacy; Electronic Communication Security; Sensitive Data; Data Loss Prevention; Data Governance.

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

The ideal combination is a Data Architect and a Data Steward. DAMA-DMBOK2 states explicitly that, ideally, both roles should be assigned to each subject area and even to individual entities within a subject area. This arrangement integrates architectural control with business accountability.

The Data Architect contributes enterprise-wide structural knowledge: subject-area boundaries, entities, relationships, integration requirements, architectural standards, and alignment with the broader Enterprise Data Architecture. The Data Steward contributes authoritative business knowledge and accountability for terminology, business rules, valid values, quality expectations, and appropriate use of the data.

DMBOK2 also describes the enterprise data model as something that should be developed and maintained jointly by Data Architects and Data Stewards working together in subject-area teams.

This pairing is especially valuable for Data Quality because structural correctness alone does not guarantee fitness for purpose. A technically valid model may still contain ambiguous definitions or inappropriate business rules. Conversely, business requirements without architectural discipline can create duplicated or inconsistent structures.

Working together, the Architect and Steward ensure that definitions, models, metadata, lineage, quality rules, and governance decisions remain aligned. DBAs, analysts, modellers, and business analysts are important contributing roles, but they do not provide the same combined architectural and governance accountability.

Reference Topics: DAMA-DMBOK2 Chapter 4 — Data Architecture Governance; Subject Areas; Chapter 3 — Data Stewardship; Enterprise Data Models; Chapter 13 — Data Quality Accountability.

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

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.

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

In a data model, entities are linked by relationships. An entity represents a distinguishable business concept or thing about which the organization stores information, while a relationship expresses how one entity is associated with another.

For example, a Customer places an Order, an Order contains Order Lines, and a Product appears on an Order Line. Relationships therefore capture business semantics rather than merely physical implementation details. Cardinality is an important characteristic of a relationship because it specifies how many instances of one entity may or must be associated with instances of another; however, cardinality is not itself the general mechanism by which entities are linked. DAMA-oriented modelling material identifies relationships as the correct linkage concept.

Indexes and triggers are physical database mechanisms. Processes describe business activities and may interact with entities, but they do not define entity-to-entity structure within a data model.

The Data Quality implications are significant. Properly defined relationships establish expectations for referential integrity. For example, an Order referencing a nonexistent Customer indicates an integrity defect. Profiling can test orphaned foreign keys, invalid relationship cardinalities, and inconsistent associations.

Relationships and their cardinalities should therefore be documented as metadata and enforced through appropriate database, application, or quality controls.

Reference Topics: DAMA-DMBOK2 Chapter 5 — Entities, Relationships and Cardinality; Logical Data Modeling; Chapter 13 — Integrity and Consistency; Metadata Management.

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

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.

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

A business-data-driven roadmap translates the desired enterprise data architecture into an executable sequence of initiatives. DAMA-DMBOK2 explains that business capabilities consume and produce data, which creates dependencies between capabilities. The roadmap begins with relatively independent capabilities and progresses toward capabilities whose execution depends on data generated elsewhere. The architecture therefore establishes a coherent dependency chain before implementation work is organized.

The decisive final planning action is to turn that dependency sequence into implementable projects. Consequently, establishing the sequence of projects that will establish the data value chain is the best answer. Describing the data value chain, analysing data flows, identifying dependency challenges, and resequencing capabilities are analytical steps that precede portfolio sequencing.

DMBOK2 states that the roadmap should move from capabilities with the least dependency toward those with progressively greater dependencies, thereby providing the implementation order. It also emphasizes integrating the Enterprise Data Architecture roadmap with enterprise milestones, resources, and business-capability workstreams.

From a Data Quality perspective, sequencing matters because upstream master and reference data must reach an acceptable quality state before downstream transactional processes can depend on it.

Reference Topics: DAMA-DMBOK2 Chapter 4 — Data Architecture; Develop a Roadmap; Data Dependencies; Data Value Chain; Chapter 13 — Data Quality and other Knowledge Areas.

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

An enterprise Master Data Repository serving multiple applications is a classic Hub-and-Spoke integration pattern. In this architecture, shared information is consolidated physically or virtually in a central hub, while participating applications interact with that hub rather than building a separate direct interface to every other application.

DAMA-DMBOK2 explicitly identifies Master Data Management hubs, Data Warehouses, Data Marts, and Operational Data Stores as familiar examples of data hubs. The hub-and-spoke model reduces the proliferation of point-to-point interfaces and can provide a consistent enterprise view of shared data.

This architecture is particularly appropriate for MDM because customer, product, supplier, location, or other master entities often need to be standardized, matched, governed, and redistributed across many systems. The central hub can apply survivorship rules, reference mappings, stewardship decisions, and quality controls before distributing trusted values.

Replication and Change Data Capture are techniques for moving or detecting changes in data, but neither describes the overall interaction topology. Publish-subscribe may operate alongside an MDM hub as a distribution mechanism, but the enterprise repository itself represents the hub within a hub-and-spoke architecture.

Reference Topics: DAMA-DMBOK2 Chapter 8 — Hub-and-Spoke; Integration Interaction Models; Chapter 10 — Master Data Management; Enterprise Master Data Hub; Data Quality Consistency.

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

Ensuring enterprise business processes are effectively documented is not primarily a Data Architecture mechanism for defining project scope boundaries. That responsibility belongs more directly to Business Architecture, process management, and business-analysis disciplines.

DAMA-DMBOK2 explains that Enterprise Data Architecture influences projects by defining enterprise data requirements, reviewing project data designs, determining lineage impacts, controlling unnecessary replication, enforcing Data Architecture standards, and guiding technology and renewal decisions.

Consequently, options A, B, D, and E all represent valid ways architecture can constrain or guide project scope. A design review checks that local solutions remain compatible with enterprise strategy. Standards prevent individual projects from creating incompatible structures. Replication controls limit uncontrolled proliferation of redundant data. Enterprise data requirements ensure that projects account for information needs beyond their immediate application boundaries.

Documenting business processes remains important because processes produce and consume data, but comprehensive process documentation is not itself a primary Enterprise Data Architecture scope-control activity.

From a Data Quality perspective, architectural influence prevents project-level decisions from creating duplicated authoritative sources, inconsistent definitions, undocumented lineage, or uncontrolled transformations.

Reference Topics: DAMA-DMBOK2 Chapter 4 — Manage Enterprise Requirements within Projects; Architecture Governance; Project Scope Boundaries; Data Replication; Chapter 13 — Consistency and Lineage.

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

DAMA-DMBOK2 states that Data Modeling tools and model repositories are necessary for managing the Enterprise Data Model at all levels. This includes maintaining relationships among conceptual, logical, and physical representations and controlling how models created for different purposes fit into the wider enterprise architecture.

An enterprise modeling repository provides more than diagramming. It supports version control, definitions, lineage between model layers, comparison of changes, reuse of standard entities and attributes, enforcement of modelling conventions, and communication across projects. Many modelling tools also provide relationship and lineage capabilities that enable architects to trace how concepts represented at a high level are implemented in detailed models.

Option C describes one important capability—visualizing and communicating database designs—but it is narrower than the DMBOK2 purpose stated in the question. Similarly, modelling tools support governance and architectural visualization but are not solely established for either function.

For Data Quality, governed models provide the structural metadata from which rules can be derived. Keys support uniqueness; relationships support integrity; domains support validity; mandatory attributes support completeness; and standardized definitions support consistency.

The repository therefore becomes an important bridge between Data Architecture, Metadata Management, Data Governance, and Data Quality.

Reference Topics: DAMA-DMBOK2 Chapter 5 — Data Modeling Tools and Repositories; Enterprise Data Model; Conceptual/Logical/Physical Models; Chapter 13 — Structural Quality Rules.

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

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.

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

The primary dimension affected is Consistency. Consistency evaluates whether equivalent information agrees across datasets, systems, representations, or related attributes when business rules require agreement.

The same customer identifier is represented with conflicting lifecycle statuses at the same time. Each value might individually satisfy its local datatype and permitted-value rules, so both could be valid in isolation. However, unless a legitimate business rule explains the difference, the two representations are inconsistent.

Resolving the issue requires more than choosing one value arbitrarily. The organization must establish the authoritative source for customer status, understand whether the systems apply different definitions of "Active" and "Closed," examine synchronization timing, and trace transformation or integration logic. Metadata should document the business meaning and source authority, while lineage should reveal how status information is propagated.

Master Data Management may also be relevant where customer-state information is shared across multiple operational systems. Governance must determine ownership and conflict-resolution rules.

DAMA's revised Chapter 13 identifies Consistency among the standardized Data Quality dimensions and explicitly strengthens its relationship with Metadata, Reference/Master Data, and Data Integration.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Consistency; Authoritative Sources; Metadata Management; Master Data Management; Data Integration.

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

The process is Encryption. DAMA-DMBOK2 defines encryption as converting readable plaintext into coded information so that privileged or sensitive content cannot be understood without the appropriate decryption mechanism. The DMBOK2 security section specifically describes encryption as translating plain text into complex codes to hide privileged information and also notes its use in protecting transmission integrity and validating identity.

Encryption supports confidentiality both at rest and in transit. Depending on implementation, organizations may use symmetric encryption, asymmetric or public-key encryption, hashing for particular integrity or authentication functions, and other cryptographic mechanisms.

The crucial distinction is that encryption deliberately changes the representation of information according to a cryptographic algorithm and key structure. Encapsulation, enhancement, elimination, and exaggeration are not substitutes for cryptographic protection.

Within the wider DAMA framework, encryption should be applied according to classification and risk. Highly sensitive information may require stronger cryptographic controls, restricted key management, rotation procedures, and separation of duties.

Data Quality and Data Security intersect at integrity: unauthorized changes may produce inaccurate data even when availability remains unaffected. Security controls therefore protect not merely secrecy but the reliability and trustworthiness of managed information.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Encryption; Confidentiality; Data Integrity; Cryptographic Controls; Security Classification.

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

Pname is Metadata because it is the name assigned to a database column and therefore describes the structure in which the actual Family Name values are stored. A value such as Smith or Patel would be data; Pname is structural information describing that data.

DAMA-DMBOK2 defines Metadata broadly as information about data and data-related processes. Technical metadata includes physical database characteristics such as table names, column names, datatypes, lengths, indexes, constraints, and related structural properties. The interpretation of Pname as metadata is also consistent with the published version of this exact certification question.

The fact that Pname may be an unclear abbreviation does not change its classification. It may represent a poor naming convention from a usability or governance perspective, but technically it remains metadata. A stronger physical name might be FamilyName, while the metadata repository could additionally map that field to the authoritative business glossary term.

This distinction matters to Data Quality because rules are frequently attached to metadata objects. For example, the Family Name attribute might have completeness, permitted-character, maximum-length, and standardization requirements.

Effective Metadata Management connects the technical column to its business meaning, system lineage, stewardship, and applicable Data Quality controls.

Reference Topics: DAMA-DMBOK2 Chapter 11 — Technical Metadata; Database Metadata; Business Glossary; Chapter 13 — Data Quality Rules and Metadata.

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

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.

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

DAMA-DMBOK2 explicitly states that Data Governance represents an inherent separation of duty between oversight and execution. It illustrates the principle through an analogy with financial governance: an auditor exercises oversight over financial processes without personally executing financial management. Similarly, Data Governance ensures that data is properly managed but does not itself perform every operational Data Management activity.

This separation is fundamental because governance must retain sufficient independence to establish rules, monitor compliance, resolve conflicts, assign accountability, and evaluate whether operational teams are managing data according to approved policies and standards.

Option B describes activities in which governance and Data Quality practitioners may collaborate, but it is not the defining governance principle. Option D is also incorrect because federated governance is only one possible operating model; DMBOK2 also recognizes centralized and replicated approaches. Option E describes an organizational implementation, not the conceptual distinction.

Within Data Quality Management, this means that governance may approve quality policies, Critical Data Elements, acceptable thresholds, stewardship structures, and escalation procedures, while DQ analysts and operational teams perform profiling, cleansing, monitoring, and remediation.

Maintaining this division reduces conflicts of interest and establishes accountability for whether data-management activities achieve agreed business objectives.

Reference Topics: DAMA-DMBOK2 Chapter 3 — Essential Concepts; Oversight versus Execution; Governance Operating Models; Chapter 13 — Data Quality Governance and Operational Responsibilities.

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

The activity is Standardization. Standardization converts semantically equivalent values into a consistent representation so they can be compared, matched, integrated, and interpreted reliably.

In the scenario, Street, St., and Str may represent the same address concept but differ syntactically. Converting them to an approved standard reduces superficial variation before entity matching.

Standardization is commonly used for names, addresses, telephone numbers, units of measure, dates, product descriptions, geographic references, abbreviations, and coded values. It frequently precedes matching and de-duplication because entity-resolution algorithms perform more effectively when predictable representational differences have already been normalized.

Reference Data and Metadata Management are important supporting disciplines. Reference Data can define approved abbreviations or formats, while metadata documents transformation rules and intended meaning.

Standardization does not prove that the resulting address is factually accurate. It improves consistency and comparability. An address can be perfectly standardized yet belong to the wrong customer.

Therefore, standardization should be combined with validation, verification, matching, and source-improvement controls where appropriate.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Standardization; Cleansing; Matching; Consistency; Reference Data Management.

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

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.

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

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.

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

The correct answer is Data models. DAMA-DMBOK2 explicitly explains that data models and other Data Architecture artifacts are commonly created or captured within development projects and are subsequently standardized and managed by Data Architects.

Development projects routinely produce conceptual, logical, and physical representations of the data required by a solution. If each project develops those structures independently without architectural review, inconsistent terminology, duplicated entities, conflicting definitions, and incompatible relationship structures can accumulate across the enterprise. Data Architects therefore review project models, reconcile them with enterprise standards, and identify structures suitable for reuse.

An Enterprise Data Model is itself an important architectural artifact, but the wording of the question refers specifically to artifacts typically generated in individual development projects and later standardized. The DMBOK2 passage uses data models in precisely that context.

This process has a direct Data Quality benefit. Standardized models improve consistency of definitions, domains, keys, relationships, and constraints. They also provide metadata from which integrity, uniqueness, validity, and completeness rules can be derived.

Reference Topics: DAMA-DMBOK2 Chapter 4 — Data Architecture; Architectural Artifacts; Development Projects; Chapter 5 — Data Modeling and Design; Chapter 13 — Consistency and Integrity.

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