Visual Atlas — Maps 09–12
Map 9 — Metadata Product Pipeline
SOURCE METADATA → HARVEST → STAGE/AUDIT → STANDARDIZE/MAP → RESOLVE CONFLICT → MANAGED STORE → DISTRIBUTE/DELIVER → FEEDBACK/QUALITY
Add a feedback arrow from consumers back to quality/maintenance.
Answer check: “Collect” is not enough. Integration/reconciliation and delivery/use are part of the product lifecycle.
Source: pp. 414–417.
Map 10 — Lineage / Impact Fork
SOURCE → TRANSFORM → TARGET → REPORT
Above the path: LINEAGE — where did it come from / where did it go?
Below the path: IMPACT — what is affected if this node changes?
Answer check: trace PII to reports = lineage; list reports/jobs affected by a rename = impact.
Source: pp. 418–419.
Map 11 — As Designed vs As Implemented
Mapping Spec / Design → AS DESIGNED
Actual Code / Jobs → AS IMPLEMENTED
Both feed an Integrated Enterprise Lineage view, with labels that preserve which evidence is intended vs actual.
Answer check: when code and design disagree about current production behavior, As Implemented reflects reality.
Source: pp. 418–419.
Map 12 — Value / Metric Evidence
Place METADATA PROGRAM EVIDENCE at the center. Add seven spokes:
- Completeness
- Maturity
- Steward Representation
- Usage
- Business Glossary Activity
- Master Data Service Compliance
- Documentation Quality
Decision rule: different spokes answer different questions. Coverage does not prove adoption; adoption does not prove quality.
Source: p. 423.
Final visual test
Rebuild Maps 2, 5, 6, 8, 9, 10, and 11 without looking. For each, state the one clue that would flip the exam answer.