DQ-1220試験に合格することは、特に良い仕事を探していて、DQ-1220認定資格を取得したい多くの人々にとって非常に重要であることがわかっています。認定資格を取得できれば、それは大いに役立つでしょう。たとえば、以前よりも会社でより多くの仕事とより良い肩書きを得るのに役立ち、DQ-1220認定資格はより高い給料を得るのに役立ちます。当社には、試験に合格し、DQ-1220試験トレントでDQ-1220認定を取得するのに役立つ能力があると考えています。
| Section | Objectives |
|---|---|
| Data Quality Assessment | - Data Profiling Techniques - Data Quality Metrics and KPIs |
| Data Quality Operations | - Monitoring and Reporting - Data Quality Tools and Technologies |
| Data Quality Management | - Data Quality Governance - Roles and Responsibilities (Data Stewardship) |
| Data Quality Improvement | - Data Cleansing Methods - Root Cause Analysis |
| Data Quality Fundamentals | - Data Quality Dimensions (Accuracy, Completeness, Consistency, Timeliness, Validity, Uniqueness) - Definition of Data Quality |
他の人はあちこちでDAMA DQ-1220試験資料を探しているとき、あなたはすでに勉強中で、準備階段でライバルに先立ちます。また、我々Topexamは量豊かのDAMA DQ-1220試験資料を提供しますし、ソフト版であなたにDAMA DQ-1220試験の最も現実的な環境をシミュレートさせます。勉強中で、何の質問があると、メールで我々はあなたのためにすぐ解決します。心配はありませんし、一心不乱に試験復習に取り組んでいます。
質問 # 17
Discovering and documenting metadata about physical data assets provides:
正解：C
解説：
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.
質問 # 18
The role of Metadata in Data Management is:
正解：D
解説：
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.
質問 # 19
Reference data is often a list of code values with their full names. One example is:
正解：B
解説：
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.
質問 # 20
Multiple data warehouses, lakes, and swamps are an indicator that the organisation values:
正解：A
解説：
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.
質問 # 21
A customer's date of birth is stored as 12/04/1980. The value conforms to the database datatype and accepted date format, but the customer's verified date of birth is 21/04/1980. Which Data Quality dimension is primarily violated?
正解：D
解説：
The primary failure is Accuracy. Accuracy concerns whether a stored value correctly represents the real- world entity, event, or fact it is intended to describe. The recorded date is syntactically acceptable and conforms to the expected datatype and format, so it may satisfy Validity while still being factually wrong.
This distinction is fundamental in Data Quality assessment. A validity rule can determine whether a value is structurally permissible-for example, whether a date conforms to an approved pattern or whether a month lies between 1 and 12. It cannot by itself prove that the date belongs to the correct person. Government guidance based on DAMA dimensions makes the same distinction: a value can be valid while remaining inaccurate.
The strongest accuracy control would compare the value with an authoritative or independently verified source. Metadata should document the authoritative source and lineage, while governance should assign responsibility for resolving discrepancies.
The scenario therefore demonstrates why Data Quality programs must avoid assuming that format compliance equals correctness.
Reference Topics: DAMA-DMBOK2 Chapter 13 - Accuracy; Validity; Authoritative Sources; Data Quality Rules; Metadata Lineage.
質問 # 22
......
この情報の時代には、DAMA業界にとても注目され、この強い情報技術業界にDAMA人材が得難いです。こうしてDQ-1220認定試験がとても重要になります。でも、この試験がとても難しくてDAMA通になりたい方が障害になっています。
DQ-1220合格対策: https://www.topexam.jp/DQ-1220_shiken.html