Stage 5 Cross-Domain Case Studies — Foundation Set
These cases are deliberately longer than the Mixed Scenarios. The goal is not merely to name a Knowledge Area; it is to produce a defensible multi-domain response in the right order.
Current inventory
- Post-Merger Customer 360 & Enterprise Reporting
- Enterprise Revenue Trust Crisis
- Regulatory Data-Control Remediation
- Legacy Warehouse to Modern Analytical Platform
Solutions stay separate: - Resolution Key — Cases 01–02 - Resolution Key — Cases 03–04
Required worksheet for every case
Before opening the solution, produce all ten layers:
- Business objective and symptoms — what outcome is required and what is going wrong?
- Leading Knowledge Area — which area organizes the response first, and why?
- Supporting Knowledge Areas — what other chapters are required?
- Roles — who is accountable, who decides, who analyzes, who implements?
- Governance decisions — what must be approved/owned before implementation?
- Architecture / design decisions — what target structures, models or patterns are needed?
- Ordered management execution — what should happen first, second, third…?
- Evidence and metrics — what proves the response is working?
- Tempting shortcut — what plausible response would fail, and why?
- Changed-fact branch — what one new fact would change the leading answer or sequence?
Scoring suggestion
- 0: identifies only a tool/technology.
- 1: names one correct Knowledge Area but misses sequencing/roles.
- 2: identifies the main domains and a mostly defensible sequence.
- 3: separates Governance/design/execution, rejects shortcuts, and handles the changed fact.
This score is a study aid, not DMBOK scoring. Only real repeated weaknesses should become later repair material.