Diagnostics MD12-052–068
MD12-052 — Correct: D
Why it wins: lineage only covers systems/processes for which sufficient Metadata is available or accessible; tool success does not create missing source coverage.
A: Lineage absolutely can include transformations.
B: Business and technical Metadata can be related.
C: Impact Analysis cannot magically fill unknown dependencies.
D: Correct.
Source: pp. 418–419. Confusion pair: lineage tool quality vs Metadata coverage.
MD12-053 — Correct: A
Why it wins: capture minimum Metadata at ingest while source, format, version, and date context is still known.
A: Correct.
B: Later reconstruction is riskier and more expensive.
C: More copies do not restore context.
D: Relational conversion is neither necessary nor sufficient for governance context.
Source: pp. 419–421. Confusion pair: ingest Metadata vs later cataloging.
MD12-054 — Correct: B
Why it wins: less-structured content often does not expose enough internal structure for discovery, provenance, security, classification, or lifecycle management.
A: Unstructured data can have known sources.
B: Correct.
C: It can be governed—with Metadata playing a key role.
D: Metadata applies to all resource types, not only relational data.
Source: pp. 402–403, 419–421. Confusion pair: unstructured data vs Metadata context.
MD12-055 — Correct: C
Why it wins: definition approval, standards enforcement, stewardship, sensitive visibility, and lifecycle quality are Governance responsibilities aligned with broader Data Governance.
A: Repository administration executes controls but does not establish decision rights/accountability.
B: Backup operations are unrelated.
C: Correct.
D: BI development does not own enterprise Metadata Governance.
Source: pp. 421–423. Confusion pair: Governance vs Repository Administration.
MD12-056 — Correct: D
Why it wins: operational stability does not establish business ownership, standards, quality, security, approval, stewardship, or accountability.
A: Governance has an ongoing lifecycle role, not only procurement.
B: Stable software cannot automatically reconcile definitions.
C: Technical admins are not automatically business owners.
D: Correct.
Source: pp. 421–423. Confusion pair: Governance roles vs technical administration.
MD12-057 — Correct: A
Why it wins: completeness compares in-scope/ideal Metadata to actual managed coverage.
A: Correct.
B: Usage asks whether people use what exists.
C: Steward representation asks whether accountable roles are assigned.
D: Glossary activity is narrower than enterprise coverage.
Source: p. 423. Confusion pair: Completeness vs Usage/Stewardship.
MD12-058 — Correct: B
Why it wins: high coverage + few searches is an adoption/usage problem, not a completeness problem.
A: Completeness is already strong.
B: Correct.
C: Retention does not explain repository adoption.
D: 11179 registration count is not the behavior metric.
Source: p. 423. Confusion pair: Usage vs Completeness.
MD12-059 — Correct: C
Why it wins: missing named Stewards and unresolved definition disputes point to Steward representation/accountability.
A: Content can exist while accountability is absent.
B: Query performance is unrelated.
C: Correct.
D: Implemented lineage is unrelated to role coverage.
Source: p. 423. Confusion pair: Steward representation vs Metadata coverage.
MD12-060 — Correct: D
Why it wins: Business Glossary activity measures use, updates, definition resolution, and related glossary behavior.
A: CDC is a change-capture method from integration/warehousing.
B: Architecture type does not measure definition activity.
C: DB availability is an operational technology metric.
D: Correct.
Source: p. 423. Confusion pair: Glossary activity vs overall usage.
MD12-061 — Correct: A
Why it wins: high coverage with duplicate/contradictory entries is a content-quality problem.
A: Correct.
B: Completeness is already high.
C: License count does not measure Metadata quality.
D: Master Data service compliance is a different metric family.
Source: p. 423. Confusion pair: Coverage vs Documentation Quality.
MD12-062 — Correct: B
Why it wins: maturity assesses the organization’s overall capability to manage Metadata, not a single inventory or activity count.
A: Harvested column count is a narrow coverage signal.
B: Correct.
C: Search count is usage.
D: Software age is not capability maturity.
Source: p. 423. Confusion pair: Maturity vs Completeness/Usage.
MD12-063 — Correct: C
Why it wins: Metadata helps developers discover reusable services and enables measurement of Master Data service reuse/compliance.
A: Service definitions remain necessary.
B: Indexes do not determine service reuse.
C: Correct.
D: Master Data services can and should be described by Metadata.
Source: p. 423. Confusion pair: service compliance/reuse vs general usage.
MD12-064 — Correct: D
Why it wins: 100% coverage answers only existence; conflicting definitions, broad sensitive visibility, and low searches are separate quality, security/Governance, and adoption failures.
A: Coverage alone does not establish program success.
B: No evidence says performance is the only or primary issue.
C: Architecture should follow requirements; switching patterns cannot automatically solve quality/security/adoption.
D: Correct.
Source: pp. 412–423. Confusion pair: Coverage vs Quality/Security/Usage.
MD12-065 — Correct: A
Why it wins: ISO/IEC 11179 is the Metadata Registry framework for standardized data-element definitions/registration and Metadata-driven exchange.
A: Correct.
B: It is not an enterprise network-security framework.
C: It does not mandate Distributed architecture.
D: It does not define backup/recovery schedules.
Source: pp. 401–402. Confusion pair: ISO 11179 vs internal technical/security standards.
MD12-066 — Correct: B
Why it wins: Socialization makes users aware of Metadata’s value and encourages participation; Access ensures they know how to find/use it.
A: Quality/Audit do not address awareness and usability directly.
B: Correct.
C: Enterprise Perspective/Commitment are important but do not best match “don’t know it exists/how to use it.”
D: Improvement handles feedback; “technical standardization” is not the paired guiding principle in the stem.
Source: pp. 398–399. Confusion pair: Socialization vs Access vs repository functionality.
MD12-067 — Correct: C
Why it wins: Chapter 12 Metadata documentation/data maps can capture source/target stores, schedules, retention/versioning, quality warnings, SOR status, retirement, people/tools, and sensitive-information handling.
A: A glossary is far too narrow.
B: A transaction log captures runtime events, not this governance landscape.
C: Correct.
D: Distributed architecture is a persistence/retrieval pattern, not the requested documentation artifact.
Source: pp. 421–422. Confusion pair: Metadata documentation/data map vs glossary/architecture.
MD12-068 — Correct: D
Why it wins: “Metadata as a product” means accountable source processes, standards, controlled change, quality monitoring, integration, delivery, and consumer feedback.
A: Passive accumulation of tool exports is the opposite of product management.
B: Write-once definitions ignore currency/change.
C: Business meaning requires business participation; technical-admin-only contribution is inadequate.
D: Correct.
Source: pp. 414–417. Confusion pair: Metadata product management vs repository-only implementation.