A digital ticketing platform's reservation service runs on Amazon EC2 instances within an Auto Scaling group (ASG) behind an Application Load Balancer (ALB). The instances are deployed in private subnets and require 6 minutes to retrieve static configuration assets and initialize the application server. During unannounced concert announcements, the platform experiences sudden flash traffic spikes, leading to HTTP 503 Service Unavailable errors on the ALB before new instances are fully operational. Furthermore, outbound API calls to third-party payment gateways fail during an outage of a single Availability Zone because all private subnets route outbound traffic through a single NAT Gateway. Which combination of actions should a solutions architect take to improve the scalability and fault tolerance of the platform? (Select TWO.)
- Deploy a NAT Gateway in each Availability Zone used by the Auto Scaling group and update the private subnet route tables to route outbound traffic through the NAT Gateway in the same Availability Zone.Cevap
- Configure an Auto Scaling group warm pool with instances in a Stopped state to maintain pre-initialized instances that can quickly transition to active service.Cevap
- CReduce the default cooldown period of the Auto Scaling group to 60 seconds to allow the group to quickly launch subsequent instances during sudden traffic spikes.
- DDeploy a single NAT Gateway in a shared public subnet across the primary Availability Zone and configure all private subnets to route outbound traffic to it to simplify network administration.
- ERequest AWS Support to pre-warm the Application Load Balancer before every anticipated flash traffic spike to ensure it scales instantly without dropping requests.