Diagnostics MD12-018–034
MD12-018 — Correct: B
Why it wins: CMDBs describe IT configuration items, versions, relationships, and technology-asset change context.
A: Business-term definitions belong in a Glossary.
B: Correct.
C: Profiles/scores are characteristic of DQ tools.
D: Mappings are characteristic of integration/mapping tools.
Source: pp. 403–407. Confusion pair: CMDB vs Metadata repository.
MD12-019 — Correct: C
Why it wins: Integration tools naturally expose mappings, transformations, technical lineage, and job execution Metadata.
A: Business approvals are glossary/governance content.
B: Endpoint policies belong more naturally to Service Registries.
C: Correct.
D: Index definitions come from DB/system catalogs.
Source: pp. 403–407. Confusion pair: Integration vs DB catalog/service registry.
MD12-020 — Correct: D
Why it wins: DQ tools produce validation rules, profiles, scores, and observed data patterns.
A: Service endpoints belong to Service Registries.
B: Patch versions are configuration/technical system Metadata.
C: Glossary workflow status is not the core DQ-tool output.
D: Correct.
Source: pp. 403–407. Confusion pair: DQ Metadata vs glossary/operations.
MD12-021 — Correct: A
Why it wins: Service Registry best fits endpoints, interfaces, operations, parameters, policies, versions, and availability.
A: Correct.
B: Glossary handles business meaning.
C: Dictionary handles data-set/element structure.
D: Reference repository handles code domains/values.
Source: pp. 406–407. Confusion pair: Service Registry vs Dictionary/Reference Data.
MD12-022 — Correct: B
Why it wins: Modeling tools/repositories store conceptual, logical, and physical model structures.
A: Messaging tools describe event interfaces/traffic.
B: Correct.
C: BI tools describe reports/calculations/usage.
D: Catalogs emphasize discovery/location.
Source: pp. 405–407. Confusion pair: Modeling repository vs metamodel/catalog.
MD12-023 — Correct: C
Why it wins: Reference Data repositories describe domains, coded values, descriptions, mappings, and relationships among reference values.
A: CMDB centers technology assets.
B: Glossary can explain concepts but is not the strongest source for code-domain relationships.
C: Correct.
D: Messaging is unrelated to value-domain stewardship.
Source: pp. 406–407. Confusion pair: Reference Data Metadata vs glossary.
MD12-024 — Correct: D
Why it wins: Centralized architecture is defined by persistent harvested copies in a common enterprise repository.
A: Distributed has no persistent central store.
B: Bi-Directional requires controlled update flow back to sources; it is not required merely for central persistence.
C: Contradicts the persistent-repository clue.
D: Correct.
Source: pp. 408–409. Confusion pair: Centralized vs Distributed.
MD12-025 — Correct: A
Why it wins: Distributed architecture provides common access while querying source repositories live and keeping no persistent central Metadata store.
A: Correct.
B: Centralized persists copies.
C: Hybrid persists selected Metadata centrally.
D: Bi-Directional concerns controlled write-back.
Source: pp. 409–410. Confusion pair: Distributed vs Centralized/Hybrid.
MD12-026 — Correct: B
Why it wins: Selected enterprise Metadata persists centrally while rapidly changing operational detail remains source-held—the defining Hybrid pattern.
A: Centralized-only would imply the chosen detail is centrally persisted rather than deliberately source-retrieved.
B: Correct.
C: Distributed-only would have no central persistent enterprise content.
D: Multiple systems do not imply Bi-Directional; write-back is missing.
Source: pp. 410–411. Confusion pair: Hybrid vs Centralized/Distributed/Bi-Directional.
MD12-027 — Correct: C
Why it wins: Controlled synchronization of enterprise changes back to a source is the Bi-Directional clue.
A: Distributed says nothing about return updates.
B: Frequent one-way refresh is still not Bi-Directional.
C: Correct.
D: A glossary is a content/source capability, not the architecture described.
Source: pp. 411–412. Confusion pair: Bi-Directional vs frequent refresh.
MD12-028 — Correct: D
Why it wins: Centralized persistence creates the burden of harvesting, adapting, synchronizing, validating, and keeping copied Metadata current.
A: Integrated search is a strength.
B: Manual enrichment is a strength, not a prohibition.
C: Real-time contact with every source characterizes Distributed retrieval, not Centralized.
D: Correct.
Source: pp. 408–409. Confusion pair: Centralized strengths vs trade-offs.
MD12-029 — Correct: A
Why it wins: Distributed architecture depends on source availability/quality and lacks persistent enterprise storage for consolidated/manual content.
A: Correct.
B: Duplication centrally is the opposite of the defining pattern.
C: Live retrieval can provide very current source Metadata.
D: Automatic write-back would be a different architecture/control capability.
Source: pp. 409–410. Confusion pair: Distributed limitations.
MD12-030 — Correct: B
Why it wins: Hybrid can preserve critical standardized Metadata centrally without continuously copying every fast-changing operational detail.
A: No architecture guarantees zero staleness.
B: Correct.
C: Hybrid may rely on source access for distributed detail.
D: Governance is not exclusive to Hybrid.
Source: pp. 410–411. Confusion pair: Hybrid rationale.
MD12-031 — Correct: C
Why it wins: When changes can occur in multiple places and flow both directions, synchronization, authority, latest version, and conflict control become harder.
A: Central search is not the special new challenge.
B: Glossary creation is independent.
C: Correct.
D: Job-log capture is unrelated to the defining synchronization risk.
Source: pp. 411–412. Confusion pair: Bi-Directional synchronization/conflict.
MD12-032 — Correct: D
Why it wins: DAMA describes broad Metadata solution layers as creation/sourcing, storage, integration, usage, and control/management.
A: Too narrow.
B: Lists business transaction processes, not Metadata lifecycle layers.
C: Lists technical functions but not the Chapter 12 lifecycle.
D: Correct.
Source: pp. 408–412. Confusion pair: architecture lifecycle layers.
MD12-033 — Correct: A
Why it wins: The high-level Chapter 12 activity sequence starts with Strategy and Requirements, then Architecture, Create/Maintain, and Use/Analyze.
A: Correct.
B: Tool-first sequence is explicitly backwards.
C: Does not match the context diagram and confuses Metadata with business data centralization.
D: Puts use before strategy and introduces a Data Warehouse activity from another domain.
Source: pp. 411–417. Confusion pair: activity sequence.
MD12-034 — Correct: B
Why it wins: Charter/scope, stakeholder interviews, current-source assessment, future architecture direction, and phased plan are Strategy work.
A: Manage Stores is operational repository administration.
B: Correct.
C: Query/Analyze is downstream use.
D: Delivery is a later sub-activity.
Source: pp. 411–413. Confusion pair: Strategy vs Architecture/operations.