Free DAMA DQ-1220 Practice Exam with Questions & Answers

Document and Content Management focuses on information stored outside conventional relational databases, including documents, images, multimedia, email, and other semi-structured or unstructured assets. Integrating this knowledge area with Data Security therefore guides the implementation of appropriate access and authorization controls for unstructured data.

DAMA's framework treats security as a cross-cutting discipline rather than something applicable only to database tables. Organizational documents can contain personally identifiable information, intellectual property, contracts, financial records, or other confidential material and therefore require the same disciplined approach to authentication, authorization, classification, retention, and monitoring as structured data. DAMA-aligned references explicitly identify appropriate access and authorization to unstructured data as the relevant interaction between these knowledge areas.

Metadata is also important because document classifications, ownership, retention category, confidentiality level, and permitted audiences provide the information needed to enforce controls.

Option A refers to structured data and therefore misses the specific contribution of Document and Content Management. Fitness-for-purpose measurement belongs primarily to Data Quality, while data-mart privacy addresses a narrower structured analytical environment.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Data Security; Chapter 9 — Document and Content Management; Unstructured Data; Access Control; Authorization; Information Classification.

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

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 failed control is principally Reasonableness. DAMA treats reasonableness as the extent to which data values or patterns conform to credible expectations. The current DMBOK2 revision recognizes Reasonableness among the standard Data Quality dimensions, alongside Accuracy, Validity, Completeness, Integrity, Uniqueness, Timeliness, Currency and Consistency.

A $100,000,000 residential electricity bill may be syntactically valid: the field may accept the number, the record may satisfy referential constraints, and the value may have arrived on time. Nevertheless, it is grossly inconsistent with the customer's historical pattern of approximately $300 per quarter. A reasonableness control would therefore compare the amount with expected ranges, historical consumption, statistical limits, peer-group distributions, or business thresholds and flag the value before billing.

This illustrates an important distinction from Accuracy. Accuracy asks whether the stored value correctly represents reality. Reasonableness asks whether the value is credible in context. The absurd magnitude itself is detectable without first obtaining an independently verified “true” bill value.

Practical controls include range checks, deviation-from-history rules, z-score/outlier detection, control limits, and exception thresholds. Such rules should be governed as metadata and owned by an appropriate Data Steward.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Data Quality Dimensions; Reasonableness; Measurement and Monitoring; Statistical Process Control; Data Quality Rules.

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

Discovering and documenting metadata about physical data assets provides visibility into how data moves and is transformed between systems. This is a core function of technical metadata and data lineage.

DAMA-DMBOK2 states that technical metadata describes the technical characteristics of data, the systems that store it, and the processes that move it within and between systems. Examples include physical table and column names, ETL job information, source-to-target mappings, and lineage documentation with upstream and downstream impact information. The certification question therefore points directly to option D; the same interpretation is independently reflected in published CDMP-oriented material.

This capability is critical to Data Quality because a defect observed in a report or downstream application may not originate in the current system. It may have been introduced through extraction logic, transformation rules, reference-data conversion, aggregation, or loading.

Documented physical metadata allows analysts to trace the affected value backward, identify its source, inspect each transformation, and isolate the point at which the defect occurred. It also supports change-impact analysis: modifying a source field or mapping can reveal which downstream assets may be affected.

Metadata therefore provides the evidence required for systematic root-cause analysis rather than symptom-based correction.

Reference Topics: DAMA-DMBOK2 Metadata Management — Technical Metadata; Source-to-Target Mapping; Data Lineage; Data Integration and Interoperability; Chapter 13 — Root-Cause Analysis and Quality Monitoring.

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

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.

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

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

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

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.

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

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.

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

The values should first be treated as potential exceptions requiring investigation. Profiling identifies anomalies; it does not automatically prove that every unusual value is incorrect or specify the appropriate remediation.

Negative age and 263 years are highly improbable for a conventional person-age attribute, suggesting a validity or reasonableness defect. However, the Data Quality team should confirm the business definition, unit of measure, derivation logic, source mappings, special-value conventions, and intended population before changing the records.

Blindly replacing values with an average introduces fabricated data and destroys traceability. Deleting the records may also remove legitimate information elsewhere in the record. Increasing the datatype range addresses technical storage rather than semantic correctness.

A disciplined Data Quality process moves from profiling to rule validation, issue assessment, root-cause analysis, remediation, and monitoring. The business rule may ultimately specify an acceptable age range, but that rule should be governed and documented rather than inferred from individual anomalies.

Metadata is essential because it should describe whether Age is stored directly, calculated from Date of Birth, or encoded using another convention.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Profiling; Validity; Reasonableness; Root-Cause Analysis; Data Quality Rules; Metadata.

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