You have a business-critical two-tier web app currently deployed in two AZs in a single region, using Elastic
Load Balancing and Auto Scaling. The app depends on synchronous replication (very low latency connectivity)
at the database layer. The application needs to remain fully available even if one application AZ goes off-line,
and Auto Scaling cannot launch new instances in the remaining Availability Zones. How can the current
architecture be enhanced to ensure this?
A.
Deploy in two regions using Weighted Round Robin (WRR), with Auto Scaling minimums set for 50 percent
peak load per Region.
B.
Deploy in two regions using Weighted Round Robin (WRR), with Auto Scaling minimums set for 100
percent peak load per region.
C.
Deploy in three Availability Zones, with Auto Scaling minimum set to handle 50 percent peak load per zone.
D.
Deploy in three Availability Zones, with Auto Scaling minimum set to handle 33 percent peak load per zone.