A statewide alerts system targets multi-site active-active DR. What implication must the architecture address beyond duplicating web tiers?
Select an answer to reveal the explanation.
Short Explanation
Two pretty front doors aren’t active-active if the filing cabinets fight each other. You need dual-Region data, conflict rules, and global routing. DNS fairy dust or static HTML mirrors won’t keep statewide alerts consistent.
Full Explanation
Multi-site active-active serves production traffic from multiple Regions simultaneously, which demands a data strategy (replication topology, conflict resolution or idempotent writes), latency-aware routing, and health-based failover. Duplicating only web tiers leaves inconsistent or unavailable state under dual writes. Claiming DNS alone prevents conflicts, skipping health checks, or freezing the second Region as static content abandons true active-active requirements for a statewide alerts platform.