Skip to content

07 — Teach-Back & Blank-Page Recall

← Question Bank · Chapter 1 Home

This is a retrieval workbook, not another reading guide. Close the Guided Learning Guide before starting a task. Attempt the answer first, then compare with the key below.

Self-scoring

  • 0 — No recall
  • 1 — Partial
  • 2 — Accurate
  • 3 — Accurate + example/distinction

A confident but inaccurate answer is a high-priority repair target.

Part I — 60-second rapid recall

  1. Define Data Management in your own words, preserving plans/policies/programs/practices, value, control/protection and lifecycle.
  2. Name at least four organizational goals and identify the one most directly about effective use for value.
  3. Explain why data is not simply “truth sitting in a database.”
  4. Explain data vs information without a rigid ladder.
  5. Give three ways data differs from physical assets.
  6. Why does managing data mean managing Data Quality?
  7. Why does it take Metadata to manage data? Give an example.
  8. Why is Data Management cross-functional rather than IT-only?
  9. What does enterprise perspective add beyond local system management?
  10. Distinguish lifecycle and lineage in one sentence each.
  11. What does ROT mean and why reduce it?
  12. State the relationship among Business Strategy, Data Strategy and Data Management Program Strategy.
  13. Distinguish Charter, Scope Statement and Implementation Roadmap.
  14. Name the four Context Diagram activity groupings.
  15. Why is Data Governance at the center of the DAMA Wheel?
  16. Name all eleven Knowledge Areas.
  17. What is the practical purpose of the Environmental Factors Hexagon?
  18. When is AIM a better lens than SAM?

Part II — 3-minute explain-and-rebuild drills

  1. Five principle buckets: rebuild the five study buckets and place the underlying DAMA principles under them.
  2. Thirteen challenges: list as many as possible; identify those most closely tied to Quality, Metadata and leadership.
  3. Valuing data: name at least five valuation approaches and classify each as cost, benefit, risk, market value or future opportunity.
  4. Quality economics: create two columns—poor-quality costs and high-quality benefits—with at least four entries each.
  5. Lifecycle map: draw planning through disposal and show why the flow can iterate.
  6. Cross-cutting controls: add Data Quality, Metadata Quality and Security across the lifecycle rather than as single stages.
  7. Strategy package: explain Charter, Scope Statement and Roadmap and give one question each answers.
  8. Context Diagram anatomy: draw inputs/suppliers → P-C-D-O activities → deliverables/consumers; add participants/tools/techniques/metrics.
  9. Framework chooser: state the problem solved by SAM, AIM, Wheel, Hexagon, Context Diagram and Aiken Pyramid.
  10. Knowledge-area organizer: group the 11 KAs in a way that helps you remember them and explain your grouping.
  11. Business + IT partnership: explain why business cannot hand all Data Management responsibility to IT.
  12. Risk and data: give examples involving confidentiality, quality and loss/unavailability.

Part III — 5-minute blank-page reconstruction

  1. Rebuild Chapter 1 as three branches: definition/value, principles/challenges, strategy/frameworks.
  2. Put the major principles across the top and connect the 13 challenges beneath them without inventing a one-to-one official mapping.
  3. Draw lifecycle + lineage + cross-cutting controls + ROT.
  4. Draw Business Strategy → Data Strategy → Program Strategy → Charter/Scope/Roadmap → projects/milestones.
  5. Create six boxes for SAM, AIM, Wheel, Hexagon, Context Diagram and Aiken Pyramid; write lens, structure and when to use.
  6. Put Data Governance in the center and place the other ten KAs around it with only relationships you can explain.
  7. Create Plan/Control/Develop/Operate columns and place at least 12 realistic activities; explain borderline cases.
  8. Give a five-minute spoken explanation to a new analyst connecting value, quality, Metadata, lifecycle, strategy, Governance and the KAs.

Part IV — Where-does-this-belong classification

Classify before checking the key:

  • C1: deciding which enterprise data capabilities should exist three years from now.
  • C2: building/testing a new integration component.
  • C3: monitoring whether a critical identifier continues to meet quality rules.
  • C4: routine production database support.
  • C5: one-page view of Business Strategy, IT Strategy and the two infrastructure/process domains.
  • C6: Business, Information and IT across strategic, tactical/structural and operational levels.
  • C7: remembering the 11 KAs plus Governance's coordinating role.
  • C8: checklist of goals/principles, roles, activities, deliverables, techniques, tools and culture for a KA.
  • C9: suppliers/inputs, activities, deliverables/consumers, participants, tools, techniques and metrics for a KA.
  • C10: capability progression showing Quality, Metadata, Architecture and Governance enabling advanced use.
  • C11: document stating overall vision, business case, goals, principles, success measures, risks and operating model.
  • C12: time-ordered programs, projects, tasks, assignments and milestones.

Reconstruction Key

Rapid recall key

  1. Data Management intentionally develops, executes and supervises plans, policies, programs and practices that deliver, control, protect and improve data/information value across lifecycles.
  2. Goals include supporting stakeholder information needs; capture/storage/protection/integrity; quality; privacy/confidentiality; preventing unauthorized/inappropriate use; effective use for value.
  3. Data represents something other than itself. Representation choices and conventions require context; Metadata records that context.
  4. Data and information are intertwined and purpose-dependent; one artifact can be information in one use and data in another.
  5. Examples: intangible, copyable, non-consuming, simultaneous use, durable, can be stolen without disappearing, difficult to recreate.
  6. Data is managed to be used; if it is not fit for stakeholder/business purpose, technical collection/storage/security alone has not created intended value.
  7. Metadata provides definitions, structures, rules, lineage, ownership and context needed to understand/manage data.
  8. Business provides meaning, priorities, use requirements, acceptable quality and value while IT provides many implementation capabilities; neither can do the entire job alone.
  9. Enterprise perspective reduces conflicting local representations/policies/priorities and helps shared data work across boundaries.
  10. Lifecycle = stages across the data's life; lineage = origin/movement/transformation path of a particular data asset.
  11. ROT = Redundant, Obsolete, Trivial; reducing it lowers cost, clutter, risk and management overhead.
  12. Business Strategy sets direction; Data Strategy identifies needed data/use; Program Strategy organizes capabilities needed to make the data reliable, secure, accessible and useful.
  13. Charter = why/mandate; Scope = what/who/horizon; Roadmap = how/when.
  14. Plan, Control, Develop, Operate.
  15. Governance provides direction, oversight, consistency, decision rights and coordination; central does not mean it performs all data work.
  16. Governance; Architecture; Modeling & Design; Storage & Operations; Security; Integration & Interoperability; Document & Content; Reference & Master; DW/BI; Metadata; Data Quality.
  17. Hexagon = recurring environmental/checklist lens surrounding Knowledge Area work around Goals & Principles.
  18. AIM is useful when you need Business, Information and IT across strategy, tactics/structure and operations; SAM is the broader four-domain alignment view.

Three-minute keys

Five principle buckets

  • Data is valuable: unique asset properties; economic value.
  • Business requirements lead: Quality; Metadata; planning; requirements drive IT.
  • Diverse skills/enterprise view: cross-functional; enterprise perspective; multiple perspectives.
  • Lifecycle/risk: lifecycle management; data types differ; risk.
  • Leadership: sustained commitment.

Thirteen challenges

Data differs from other assets; valuation; Data Quality; planning; Metadata; cross-functional management; enterprise perspective; other perspectives; lifecycle; different data types; risk; technology; leadership/commitment.

Valuation examples

Acquisition/storage cost; replacement cost; impact of missing data; risk-mitigation value; cost of improvements; benefits of higher quality; competitor value; sale value; innovative-use revenue.

Quality economics

Poor quality: rework, workarounds, inefficiency, conflict, dissatisfaction, missed opportunity, compliance exposure, reputational damage.
High quality: customer experience, productivity, risk reduction, opportunity capture, revenue, competitive insight.

Lifecycle + cross-cutting controls

A reconstruction may use Plan → Design & Enable → Create/Obtain → Store/Maintain → Use → Enhance → Dispose; the current Visual Atlas uses the simpler plan/create/store/use/transform/share/dispose memory map. In either case, show iteration and keep Quality, Metadata Quality and Security as cross-cutting concerns. Lineage traces a specific data path.

Strategy package

Charter = why/mandate; Scope Statement = what/who/horizon; Roadmap = when/how initiatives and milestones execute.

Context Diagram anatomy

Definition/goals + activities at center; Inputs/Suppliers → Activities → Deliverables/Consumers; Participants/Tools/Techniques/Metrics support or evaluate; activity categories P-C-D-O.

Framework chooser

SAM = four-domain business/IT alignment; AIM = Business/Information/IT × organizational level; Wheel = KAs + Governance center; Hexagon = recurring environmental factors; Context Diagram = KA operating anatomy; Aiken = capability progression/dependencies.

Five-minute success criteria

  • Your mental skeleton should include purpose/value/definition, principles/challenges, strategy/frameworks/KAs.
  • Do not invent an official one-to-one principle→challenge mapping.
  • Lifecycle should include planning through disposal, iteration, lineage, Quality, Metadata Quality, Security and ROT.
  • Strategy drawing should show Business Strategy driving Data Strategy, Program Strategy enabling it, then Charter/Scope/Roadmap translating direction to execution.
  • Identify frameworks by purpose rather than memorizing geometry.
  • Include all 11 KAs; Governance can be central only with an explanation of what “central” means.
  • P-C-D-O should remain direction / assurance / build-change / run-support.

Classification answer key

ID Answer Decisive clue
C1 Plan future capability/direction
C2 Develop build/test/deploy
C3 Control ongoing quality assurance
C4 Operate production use/maintenance
C5 SAM four-domain business/IT alignment
C6 AIM 3×3 Business/Information/IT by level
C7 DAMA Wheel 11 KAs + Governance center
C8 Environmental Factors Hexagon recurring factors/checklist around a KA
C9 Knowledge Area Context Diagram inputs/activities/outputs/roles/supporting mechanisms
C10 Aiken DMBOK Pyramid capability progression/dependencies
C11 Data Management Charter vision/business case/goals/operating model
C12 Implementation Roadmap time-ordered initiatives/tasks/milestones

Repair protocol after a miss

  • Knowledge gap: reread only the relevant section, close it, reteach it from memory, then answer two fresh prompts.
  • Vocabulary confusion: write the DAMA term, plain-language meaning, an example and a contrast.
  • Confusion pair: revisit the Battle Card and classify two contrasting scenarios.
  • Sequence/process error: redraw the process from memory and explain each stage.
  • Missed qualifier / poor elimination: identify the decisive wording and explain why each rejected option fails.
  • Confidently wrong: schedule high-priority spaced retesting.

← Question Bank · Chapter 1 Home