Diagnostics MD12-035–051
MD12-035 — Correct: C
Why it wins: term search/ownership, lineage/versioning, and restricted views are consumer/content/access/control needs that must be consolidated during Requirements.
A: Create/Maintain comes after requirements define what must be managed.
B: Querying is only one downstream use.
C: Correct.
D: Completeness measures scope coverage, not requirements definition.
Source: pp. 412–413. Confusion pair: Requirements vs Architecture/Create-Maintain.
MD12-036 — Correct: D
Why it wins: Metadata can reveal existence, location, structure, ownership, or security context of highly protected data even without exposing values.
A: Metadata is itself data and can require controls.
B: Sensitive exposure can occur in technical/catalog Metadata too.
C: Security applies to Metadata access itself, not only exports.
D: Correct.
Source: pp. 412–413. Confusion pair: Metadata Security vs Data Security.
MD12-037 — Correct: A
Why it wins: A metamodel is the data model for the Metadata environment, representing Metadata entities, attributes, and relationships.
A: Correct.
B: Master Data records are business data, not a metamodel definition.
C: Transaction lists are data, not Metadata-model structure.
D: Network diagrams may be Metadata but are not the metamodel concept.
Source: pp. 413–414. Confusion pair: Metamodel vs Data Model.
MD12-038 — Correct: B
Why it wins: Strategy and requirements determine what Metadata must be managed; the metamodel is then created within architecture to represent that scope.
A: Building it before needs are understood is tool/model-first design.
B: Correct.
C: Retirement is far too late.
D: It is an architecture/design artifact, not only an audit artifact.
Source: pp. 413–414. Confusion pair: metamodel timing.
MD12-039 — Correct: C
Why it wins: inconsistent naming/visibility conventions are a Metadata standards problem; Governance monitors compliance.
A: Replacing source systems is excessive and does not solve enterprise conventions directly.
B: Stopping integration abandons the goal rather than controlling differences.
C: Correct.
D: Classification as Operational Metadata is unrelated.
Source: pp. 413–414. Confusion pair: Apply Standards vs Manage Stores.
MD12-040 — Correct: D
Why it wins: a failed harvest job, warnings, and stale source content are repository movement/update operations handled through Manage Metadata Stores.
A: Strategy direction is not the immediate failure.
B: Creating terms does not repair the harvest.
C: Steward representation is a governance metric, not the operational issue.
D: Correct.
Source: p. 414. Confusion pair: Manage Stores vs Governance/Strategy.
MD12-041 — Correct: A
Why it wins: managing Metadata as a product means deliberate accountable creation, standards, quality, maintenance, integration, delivery, and feedback—not accidental tool exhaust.
A: Correct.
B: “Product” does not mean externally selling Metadata.
C: The content/lifecycle—not merely repository software—must be managed.
D: Metadata must change under control as sources/business meaning change.
Source: pp. 414–416. Confusion pair: Metadata product vs repository tool.
MD12-042 — Correct: B
Why it wins: heterogeneous source Metadata must be staged, standardized, mapped, conflicts resolved, and merged under controls.
A: Publishing conflicts transfers the integration problem to users.
B: Correct.
C: Source Metadata remains valuable evidence and should not simply be deleted.
D: The business data does not belong in the Metadata repository merely because its Metadata conflicts.
Source: pp. 414–416. Confusion pair: Integrate Metadata vs unmanaged source aggregation.
MD12-043 — Correct: C
Why it wins: staging supports controlled integration, rollback/recovery, and an interim audit trail for source/quality investigation.
A: Staging is not the permanent consumer presentation layer.
B: It does not eliminate source Metadata.
C: Correct.
D: Staging supports rather than avoids quality controls.
Source: pp. 414–416. Confusion pair: Metadata staging vs managed repository/delivery.
MD12-044 — Correct: D
Why it wins: trusted content that consumers cannot access indicates failure in Distribute and Deliver Metadata.
A: Metamodel design is not the missing user-access capability.
B: Standards quality can already be sound.
C: Lineage is a content/use case, not the broad access solution.
D: Correct.
Source: pp. 415–417. Confusion pair: Delivery vs Integration/collection.
MD12-045 — Correct: A
Why it wins: Chapter 12 allows many delivery channels—portals, reports/glossaries/docs, application/BI layers, files, and web services.
A: Correct.
B: DBA-only access is unnecessarily restrictive and not the chapter model.
C: Paper-only delivery is too narrow.
D: A repository GUI is only one possible interface.
Source: pp. 415–417. Confusion pair: delivery mechanisms.
MD12-046 — Correct: B
Why it wins: business and technical consumers may need different terminology, detail, content, and analytical views over the same managed foundation.
A: Business users may consume technical Metadata such as lineage.
B: Correct.
C: Technical users also need business definitions.
D: Chapter 12 does not require a single interface.
Source: pp. 416–417. Confusion pair: consumer views vs Metadata type.
MD12-047 — Correct: C
Why it wins: a mapping specification documents intended flow, therefore As Designed Lineage.
A: As Implemented requires actual code/production evidence.
B: The mapping is technical design, not merely runtime Operational Metadata.
C: Correct.
D: Impact Analysis concerns consequences of a proposed change.
Source: pp. 418–419. Confusion pair: As Designed vs As Implemented.
MD12-048 — Correct: D
Why it wins: scanner evidence from production ETL code describes actual implemented processing.
A: Designed lineage comes from specifications/models.
B: A glossary does not establish the execution path.
C: Completeness is a metric, not lineage type.
D: Correct.
Source: pp. 418–419. Confusion pair: As Implemented vs As Designed.
MD12-049 — Correct: A
Why it wins: when design and code disagree, actual code is current production reality; the mapping remains evidence of intent.
A: Correct.
B: Designed lineage alone would misstate current execution.
C: Business definition cannot prove processing path.
D: Usage measures adoption, not production lineage.
Source: pp. 418–419. Confusion pair: design vs production reality.
MD12-050 — Correct: B
Why it wins: origin, transformations, and downstream destinations are a Data Lineage question.
A: Impact asks consequences of a proposed change rather than the current path.
B: Correct.
C: Maturity scoring is program capability evidence.
D: Steward representation concerns role coverage.
Source: pp. 418–419. Confusion pair: Lineage vs Impact.
MD12-051 — Correct: C
Why it wins: proposed rename + affected jobs/targets/reports/apps is exactly Impact Analysis using dependency Metadata.
A: Lineage relationships are inputs, but “lineage only as an end” does not answer the consequence question.
B: Glossary activity is unrelated.
C: Correct.
D: Completeness measures coverage, not affected assets.
Source: pp. 418–419. Confusion pair: Impact vs Lineage.