Skip to content

Blank-Page Reconstructions

Attempt each on a blank page before opening the key below.

Prompts

  1. Draw the Metadata knowledge web: data in the center with meaning, systems, processes, rules, people/owners, quality/security, and lineage around it.
  2. Draw the Business / Technical / Operational Metadata triangle and add three examples to each corner.
  3. Draw the Business Glossary / Data Dictionary / Directory-Catalog comparison.
  4. Draw all four Metadata architectures and mark where Metadata persists and how updates flow.
  5. Write the five Metadata Management activities in order and place sub-activities beneath the right stage.
  6. Draw Strategy → Requirements → Architecture → Metamodel/Standards → Create/Maintain → Deliver/Use.
  7. Draw the Metadata source landscape with at least ten of the 15 source families feeding the managed environment.
  8. Draw the integration pipeline: harvest → stage/audit → standardize/map → resolve conflict → managed store → deliver → feedback.
  9. Draw Data Model vs Metamodel using example entities.
  10. Draw As Designed and As Implemented lineage as parallel paths into an integrated enterprise lineage view.
  11. Draw one data path and show how Lineage and Impact Analysis ask different questions of the same dependencies.
  12. Draw the seven metric families around “Metadata Program Evidence.”

Reconstruction Key

  1. Knowledge web: DATA center → Business Meaning, Systems, Processes, Rules, People/Owners, Quality/Security, Lineage.
  2. Types: Business = definition/rule/Steward; Technical = table/mapping/schema; Operational = job log/error/query duration.
  3. Meaning/Detail/Discovery: Glossary = business meaning; Dictionary = element structure; Catalog = location/discovery.
  4. Architectures: Centralized = source copies→persistent repo; Distributed = portal→live sources/no repo; Hybrid = selected central + live detail; Bi-Directional = controlled source↔repository updates.
  5. Activities: Strategy → Requirements → Architecture → Create/Maintain → Query/Report/Analyze. Under Architecture: Metamodel, Standards, Manage Stores. Under Create/Maintain: Integrate, Distribute/Deliver.
  6. Lifecycle: Strategy → Requirements → Architecture → Metamodel/Standards → Create/Maintain → Delivery/Use, with Governance/Security/Quality across the chain.
  7. Sources: any 10+ of the 15 count; anchor with Glossary, Dictionary/Catalog, Integration, DBMS, Modeling, DQ, CMDB.
  8. Integration: Harvest → Stage/Audit → Standardize/Map → Resolve Conflict → Managed Store → Deliver → Feedback/Quality.
  9. Model: Customer/Order/Product. Metamodel: System/DataSet/DataElement/Mapping/Steward.
  10. Designed: mapping/specifications. Implemented: actual code/jobs. Enterprise view combines actual where available and design to augment labeled gaps.
  11. Data path Source → Transform → Target → Report. Lineage traces path; Impact starts with proposed change and identifies dependent nodes.
  12. Completeness, Maturity, Steward Representation, Usage, Glossary Activity, Master Data Service Compliance, Documentation Quality.

Scoring: full credit requires structure and the decision rule.

← Recall Key 41–80 · Classification →