Skip to content

Compression Teach-Back & Repair

Compression 1 — Five minutes

Teach the chapter using this path without notes:

Reference vs Master → authority concepts → MDM processing → matching/errors/workflows → identifiers/relationships → Registry/Transaction Hub/Consolidated → RDM change → stewardship/sharing → governance/metrics.

You should be able to give at least one example and one exam trap for every segment.

Compression 2 — Two minutes

Teach only the highest-risk distinctions: - Reference/Master/Transaction/Metadata; - SOR/System of Reference; - Trusted Source/Golden Record; - false positive/false negative; - deterministic/probabilistic; - duplicate identification/match-link/match-merge; - Global ID/Source ID/X-Ref; - Registry/Transaction Hub/Consolidated; - standardization/enrichment/entity resolution; - sharing agreement/interface; - SLA/DQ; - tool implementation/MDM program.

Compression 3 — Thirty seconds

Chapter 10 creates shared enterprise context by governing domain values and reconciling the identity of core entities, then distributing trusted data through controlled architecture, stewardship, sharing, governance, and measurement.

Self-score

For each recall/rebuild/classification: - 0 = blank or wrong - 1 = partial / familiar term but missing deciding clue - 2 = correct with the deciding clue - 3 = can handle a changed-fact scenario and explain why the answer switches

Repair protocol

  1. Do not pre-build Artifact 08 from predicted weakness.
  2. Record real 0–1 items, repeated slow decisions, confidence errors, and question-bank misses.
  3. Tag the confusion pair: e.g., SOR/System of Reference, false+/false−, link/merge, Registry/Consolidated.
  4. Return to the smallest relevant lesson/map/battle card rather than rereading the entire chapter.
  5. Rebuild the concept from memory.
  6. Retest 24–72 hours later without rereading first.
  7. Promote to stable only when you can reach score 2–3 repeatedly.

High-value repair targets

  • If data-type classification is weak → redraw Map 1 and do classification clues 1–4.
  • If authority is weak → redraw Map 3 and explain changed write authority.
  • If matching is weak → redraw Maps 6–8 and classify false+/false−, flag/link/merge, Global/X-Ref.
  • If architecture is weak → redraw Map 9 and state who owns writes in each pattern.
  • If RDM change is weak → write request→stakeholders→impact→decision→update→communication from memory.
  • If “technology = program” errors recur → teach the governance loop and metric families.

← Classification Drill · Chapter Home