Blank-Page Reconstructions A–I
Complete each from memory before reading its key.
Rebuild A — The chapter spine
Draw Business Continuity → three goals → Technology Support / Operations Support → governance.
Rebuild B — Role map
Place Production, Application, Procedural, Development DBA, and NSA around their responsibilities.
Rebuild C — Architecture map
Draw Centralized vs Distributed; split Distributed into Federated vs Non-federated; split Federated into Loose vs Tight.
Rebuild D — Processing map
Write ACID, BASE, CAP and explain what question each answers.
Rebuild E — Environment map
Draw Development → Test/QA → Production; put Sandbox beside it with no-write-back boundary.
Rebuild F — Lifecycle map
Connect Retention → Active Storage → Archive → Purge with legal/business/risk decision points.
Rebuild G — Continuity map
Criticality → SLA → Backup → Off-site/separate copy → Restore Test → Recovery/Failover.
Rebuild H — Performance triage
Availability + Speed → monitoring → statistics/SQL/indexes/resources/workload → remediation.
Rebuild I — Governance map
Storage / Performance / Operational / Service metrics + asset tracking + audit + validation.
Reconstruction Key — minimum correct skeleton
| Rebuild | Minimum skeleton |
|---|---|
| A | Business continuity; goals = availability, integrity, transaction performance; Technology vs Operations Support |
| B | Production = reliability/backup/failover; Application = application DBs; Procedural = stored logic; Development = design/sandbox; NSA = arrays |
| C | Centralized one system; Distributed multiple nodes; Federated autonomous; Non-federated central control; Loose component-built; Tight integrated/published schema |
| D | ACID Atomicity/Consistency/Isolation/Durability; BASE Basically Available/Soft state/Eventual consistency; CAP Consistency/Availability/Partition tolerance |
| E | Development first; Test formal QA/UAT/integration/performance; Production last/live; Sandbox isolated experiment, no Production writes |
| F | Retention defines time; archive retains retrievability; purge is irreversible |
| G | Criticality sets priority; backups follow service need; separate/off-site copies; restore tests prove recoverability; failover/restore as designed |
| H | Performance = availability + speed; investigate evidence such as memory, locks, statistics, SQL, indexes, load, volatility, runaway queries |
| I | four metric families; asset/license/TCO tracking; audit = compliance; validation = quality/usability |