A gaming company hosts a backend platform for real-time multiplayer tournaments on Amazon EC2 instances in an Auto Scaling group (ASG) behind an Application Load Balancer. The ASG is distributed across two Availability Zones: us-east-1a and us-east-1b. The instances reside in private subnets, and all outbound traffic is routed through a single NAT Gateway located in us-east-1a.
The instances require approximately to download a asset bundle, extract game assets, and complete custom bootstrapping before passing health checks. The company experiences two challenges:
1. During scheduled tournaments, load increases instantly. The ASG initiates scaling, but connection drops occur during the first of the event. Because the default cooldown is set to , the ASG continuously launches unnecessary instances while the first batch is still bootstrapping, which dramatically increases operational costs.
2. During an outage in us-east-1a, the NAT Gateway became unavailable, causing backend instances in us-east-1b to fail outbound calls to a third-party analytics API, rendering the entire game offline.
Which combination of actions will resolve these scaling and reliability issues while minimizing costs and maintaining fault tolerance? (Choose two.)
- Configure an Amazon EC2 Auto Scaling warm pool for the ASG with instances kept in the Stopped state, and set the instance warmup value of the target tracking scaling policy to .Cevap
- Deploy a new NAT Gateway in us-east-1b, and configure the route table for the private subnets in us-east-1b to route external traffic () through this new NAT Gateway.Cevap
- CDeploy a secondary NAT Gateway in us-east-1a, and configure Route 53 DNS routing rules to split the outbound traffic between both NAT Gateways.
- DDecrease the ASG default cooldown period from to to trigger faster subsequent scaling activities during traffic spikes.
- ESubmit an Application Load Balancer (ALB) pre-warming request to AWS Support at least before tournaments, and set the scaling policy's instance warmup to .