Skip to content

7 — Independent Rebuild, Evidence & Closed-Book Debrief

← Knowledge Areas & Changed Fact · Lab Home · Next → Answer Key & Completion

Rebuild independently — remove the template

Close the detailed lab instructions. From a blank document or whiteboard, rebuild a smaller equivalent of the Chapter 1 reasoning:

  1. Name five Meridian data assets and explain why each is an enterprise asset.
  2. Rank the five by value/risk and defend the ranking.
  3. Draw one data lifecycle and label at least four management responsibilities across it.
  4. Take one messy-company issue and state the business/data requirement before the tool.
  5. Recreate the distinction among Charter, Scope Statement, and Roadmap.
  6. Name the lead Knowledge Area for three Meridian issues and one supporting area for each.

Independence gate: You do not need to reproduce exact wording or table design. You do need to reproduce the reasoning structure and explain why each step is Data Management work.

Save / prove — evidence checklist

Create or link the following evidence:

  • CH01-A — Meridian Data Asset Inventory
  • CH01-B — Value & Risk Assessment
  • CH01-C — Lifecycle Management Map
  • CH01-D — Business/Data Requirements Before Technology
  • CH01-E — Data Management Charter, Scope & Roadmap
  • CH01-F — Knowledge Area Map & DMBOK Debrief
  • CH01-G — Acquisition Change-Fact Revision

A screenshot without reasoning does not satisfy the lab. Update status only after you can explain the evidence.


Closed-book DMBOK debrief

Answer these before opening the reconstruction key:

  1. Why is Meridian's customer problem a Data Management problem even before deciding which system should store a trusted customer record?
  2. Why does a data-asset inventory need business-process, consumer, and Metadata context rather than only a list of tables?
  3. How did the value/risk exercise demonstrate that data differs from a physical asset?
  4. Explain lifecycle vs lineage using one Meridian data asset.
  5. Give one example where a business/data requirement should be settled before a technology decision.
  6. Why are the Charter, Scope Statement, and Roadmap three different artifacts?
  7. Why can Data Governance be central without being the same as all Data Management?
  8. What changed in your priorities after the acquisition scenario, and which Chapter 1 principle best explains the change?

Do not open the next page until you have attempted all eight.