Diagnostics MD12-001–017
Use only after attempting the corresponding practice set.
MD12-001 — Correct: A
Why it wins: Chapter 12 defines Metadata Management broadly as planning, implementation, and control that enables processing, maintenance, integration, security, audit, and governance of other data.
A: Correct—the scope is enterprise management, not one artifact.
B: Too narrow; a glossary is only one Metadata capability/source.
C: Confuses Metadata Management with copying business data into a repository.
D: Too narrow; technical column definitions are only one Metadata type.
Source: pp. 395–398. Confusion pair: Metadata Management vs glossary/tool.
MD12-002 — Correct: B
Why it wins: The library-catalog analogy is about making information discoverable, understandable, related, and governable even when the underlying resources already exist.
A: Metadata does not replace the resources it describes.
B: Correct.
C: The analogy does not mandate literal library classification standards.
D: Too narrow; Chapter 12 extends beyond descriptive document Metadata.
Source: pp. 395–398. Confusion pair: Metadata vs data/resource.
MD12-003 — Correct: C
Why it wins: Collecting and integrating diverse Metadata sources is an explicit program goal.
A: Metadata Management complements rather than eliminates Data Governance.
B: Access must consider security; all Metadata should not automatically be public.
C: Correct.
D: Keeping Metadata isolated in source tools prevents enterprise integration.
Source: pp. 397–399. Confusion pair: goals vs source/tool silos.
MD12-004 — Correct: D
Why it wins: Quality, consistency, currency, and security are explicit Metadata Management goals.
A: Metadata contextualizes data; it does not replace operational data.
B: Centralizing applications is not the goal.
C: Chapter 12 calls for technical standards rather than removing them.
D: Correct.
Source: pp. 397–399. Confusion pair: quality/currency/security vs architecture.
MD12-005 — Correct: A
Why it wins: The Strategy principle requires enterprise direction and requirements before product evaluation/installation.
A: Correct.
B: Socialization concerns communicating value and participation.
C: Audit concerns standards/compliance checking.
D: Improvement concerns feedback and correction of bad/stale Metadata.
Source: pp. 398–399. Confusion pair: Strategy vs tool selection.
MD12-006 — Correct: B
Why it wins: Enterprise Perspective means designing for enterprise extensibility while implementing iteratively/incrementally.
A: Audit is not about phased enterprise delivery.
B: Correct.
C: Access concerns finding/using Metadata.
D: Organizational Commitment concerns sponsorship/funding/support.
Source: pp. 398–399. Confusion pair: enterprise perspective vs big bang.
MD12-007 — Correct: C
Why it wins: Improvement requires feedback mechanisms through which consumers can identify and correct stale/incorrect Metadata.
A: Commitment is sponsorship/support, not the missing correction channel.
B: Enterprise Perspective is scope/design orientation.
C: Correct.
D: Audit tests standards/compliance but does not itself supply the user feedback loop described.
Source: pp. 398–399. Confusion pair: Improvement vs Audit.
MD12-008 — Correct: D
Why it wins: DAMA explicitly treats Metadata as data and warns that the boundary can depend on context/abstraction.
A: False audience/type split.
B: Storage location does not define data vs Metadata.
C: Metadata can and should be governed using data-management principles.
D: Correct.
Source: pp. 397–399. Confusion pair: Metadata vs data.
MD12-009 — Correct: A
Why it wins: Approved definitions and Stewardship are classic Business Metadata.
A: Correct.
B: VARCHAR length is Technical Metadata.
C: Runtime duration is Operational Metadata.
D: Patch level is technical/operational system context, not business meaning.
Source: pp. 399–401. Confusion pair: Business vs Technical vs Operational.
MD12-010 — Correct: B
Why it wins: Source-to-target mappings describe technical implementation/movement.
A: Glossary definition is Business Metadata.
B: Correct.
C: Failed-row count is Operational Metadata.
D: User-satisfaction survey is program/adoption evidence, not Technical Metadata.
Source: pp. 399–401. Confusion pair: Technical vs Business/Operational.
MD12-011 — Correct: C
Why it wins: Extraction timestamp/result is runtime processing evidence.
A: Approved definition is Business Metadata.
B: Logical business relationship is model/Technical Metadata rather than runtime evidence.
C: Correct.
D: Business owner is Business Metadata.
Source: pp. 399–401. Confusion pair: Operational vs Business/Technical.
MD12-012 — Correct: D
Why it wins: Query execution time and access frequency describe runtime/access behavior.
A: They do not define business meaning.
B: They are not controlled code/value domains.
C: They are not core enterprise entities.
D: Correct—Operational Metadata.
Source: pp. 399–401. Confusion pair: Operational Metadata vs business data.
MD12-013 — Correct: A
Why it wins: Structural Metadata describes how parts of a resource relate.
A: Correct—page/chapter relationships are structural.
B: Author/subject is Descriptive Metadata.
C: Archive date is Administrative Metadata.
D: Steward approval is Business Metadata/governance context, not this information-science structural category.
Source: pp. 401–402. Confusion pair: Structural vs Descriptive/Administrative.
MD12-014 — Correct: B
Why it wins: ISO/IEC 11179 is presented as a Metadata Registry framework supporting standardized data-element definitions and Metadata-driven exchange.
A: It does not define the four architecture patterns.
B: Correct.
C: It does not mandate Distributed architecture.
D: It is not a DQ scoring standard.
Source: pp. 401–402. Confusion pair: ISO 11179 vs architecture/quality standard.
MD12-015 — Correct: C
Why it wins: Business Glossary is the strongest source for business meaning and ownership.
A: System catalog is stronger for physical DB structures.
B: CMDB is stronger for IT configuration assets.
C: Correct.
D: Messaging tools describe event interfaces/movement, not term governance.
Source: pp. 403–407. Confusion pair: Glossary vs Dictionary/Catalog.
MD12-016 — Correct: D
Why it wins: Datatype, default, storage, relationships, and uniqueness are data-element structural characteristics handled by a Data Dictionary.
A: Glossary centers business concepts/meaning.
B: Service Registry centers service interfaces/endpoints.
C: BI catalog centers analytical/report artifacts.
D: Correct.
Source: pp. 403–407. Confusion pair: Dictionary vs Glossary/Catalog.
MD12-017 — Correct: A
Why it wins: Directory/Catalog supports enterprise discovery of systems, data sources, and locations.
A: Correct.
B: Dictionary provides element detail but is not the strongest enterprise-location answer.
C: Business-rule repository explains rules, not where assets reside.
D: Job log provides runtime evidence, not discovery.
Source: pp. 403–407. Confusion pair: Catalog vs Dictionary.