DQ-1220 Dumps with Practice Exam Questions Answers

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.

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

DAMA-DMBOK2 defines Data Governance as the exercise of authority and control over the management of data assets. This definition distinguishes governance from the operational execution of Data Management. Independent literature describing DAMA's framework uses the same core formulation, and the DAMA Wheel places Data Governance across the other knowledge areas through this authority-and-control function.

Governance establishes decision rights, accountability, policies, standards, stewardship, issue escalation, compliance expectations, and mechanisms for monitoring whether data is being managed appropriately. It determines who is authorized to make decisions and what rules must be followed; individual Data Management knowledge areas then execute the corresponding operational activities.

Option E is closer to the broad definition of Data Management, because it refers to planning, implementation, and control across the information lifecycle. Option A describes an assessment or maturity activity. Option B describes selected governance benefits rather than its definition, while option C characterizes a collection of functions.

For Data Quality, governance provides the authority needed to define critical data, approve quality requirements and thresholds, assign accountability, prioritize remediation, and enforce standards. Without this authority structure, profiling may identify defects but the organization may lack the decision mechanisms required to correct their underlying causes.

Reference Topics: DAMA-DMBOK2 Chapter 3 — Data Governance Definition; Authority and Control; Policies and Standards; Chapter 13 — Data Quality Governance.

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

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.

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

Effective security risk reduction begins by understanding what data exists, how sensitive or critical it is, and where it resides. A classification model provides this foundation by classifying data concepts according to protection requirements and linking those concepts to their physical implementations. The certification material reflects this DAMA principle directly.

Data cannot be protected proportionately if the organization does not know whether it represents public information, internal operational information, personally identifiable information, financial data, intellectual property, regulated information, or another sensitive category. Classification allows the organization to apply appropriate controls according to risk rather than treating every data asset identically.

Once classification is established, security teams can define access requirements, encryption needs, monitoring, retention controls, masking, authorization policies, and other safeguards. Metadata is essential because classifications must ultimately be connected to actual databases, files, attributes, interfaces, and repositories.

A firewall alone does not provide data-level protection, and role classification by itself addresses only one dimension of security. Similarly, an Enterprise Data Model describes organizational data structures but does not replace security classification.

Reference Topics: DAMA-DMBOK2 Chapter 7 — Data Security; Data Classification; Risk Reduction; Sensitive Data Discovery; Metadata Management; Chapter 13 — Integrity and Controlled Use.

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

Critical Data Elements are identified so that organizations can concentrate governance and Data Quality effort where failure would create the greatest business impact.

Not every attribute deserves the same level of profiling, monitoring, stewardship, lineage documentation, control, and remediation. Applying identical controls to every field would usually be economically inefficient and may divert resources away from information that supports regulation, financial reporting, key operations, customer outcomes, or strategic decisions.

The DMBOK2 maintenance revision explicitly adds and clarifies the concept of a Critical Data Element within Chapter 13.

Once a CDE is identified, the organization can define applicable quality dimensions, measurable rules, thresholds, ownership, authoritative sources, lineage, issue escalation, and monitoring frequency.

Criticality is contextual. An attribute may be critical to one process and relatively insignificant to another. The decision should therefore reflect documented business use and risk rather than technical prominence.

Metadata remains essential because it links the CDE to definitions, systems, lineage, owners, and quality controls.

Reference Topics: DAMA-DMBOK2 Chapter 13 — Critical Data Elements; Prioritization; Business Impact; Risk; Data Governance; Metadata.

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