During a business continuity tabletop, leaders ask how the city would operate if an entire AWS Region were impaired. What strategy should be discussed?
Select an answer to reveal the explanation.
Short Explanation
Tabletop question: whole Region is gone—another subnet next door will not help. Leaders should talk multi-Region so continuity lives beyond one geography. Ignoring alarms or parking state on one instance's local disk makes a bad day worse.
Full Explanation
Business continuity planning for Region-wide events requires strategies that span multiple AWS Regions. Multi-AZ designs remain valuable for AZ failures but assume the Region itself is usable. Civic tabletop exercises should explicitly cover multi-Region failover, data replication, and recovery runbooks. Disabling monitoring or using ephemeral single-host storage undermines continuity rather than supporting it.