Soru

Zorluk: ZorImplementing Auto Scaling and Fault Tolerance

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 6 minutes6\text{ minutes} to download a 4 GB4\text{ GB} 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 10 minutes10\text{ minutes} of the event. Because the default cooldown is set to 180 seconds180\text{ seconds}, 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.)

  1. 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 420 seconds420\text{ seconds}.Cevap
  2. 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 (0.0.0.0/00.0.0.0/0) through this new NAT Gateway.Cevap
  3. C
    Deploy a secondary NAT Gateway in us-east-1a, and configure Route 53 DNS routing rules to split the outbound traffic between both NAT Gateways.
  4. D
    Decrease the ASG default cooldown period from 180 seconds180\text{ seconds} to 60 seconds60\text{ seconds} to trigger faster subsequent scaling activities during traffic spikes.
  5. E
    Submit an Application Load Balancer (ALB) pre-warming request to AWS Support at least 24 hours24\text{ hours} before tournaments, and set the scaling policy's instance warmup to 120 seconds120\text{ seconds}.

Cevap

The correct actions are to configure an Amazon EC2 Auto Scaling warm pool for the ASG with instances in the Stopped state while setting the instance warmup value of the scaling policy to 420 seconds420\text{ seconds}, and to deploy a new NAT Gateway in us-east-1b while routing external traffic from the us-east-1b private subnets through it.
Configuring an EC2 Auto Scaling warm pool with instances in the Stopped state ensures that pre-bootstrapped instances can be quickly started to handle traffic spikes, bypassing the 6 minutes6\text{ minutes} bootstrapping delay. Setting the scaling policy's instance warmup to 420 seconds420\text{ seconds} (which is greater than the 360 second360\text{ second} boot time) prevents premature secondary scaling actions. Deploying a NAT Gateway in us-east-1b and configuring local subnet route tables ensures that an outage in us-east-1a does not interrupt outbound traffic from us-east-1b.

Adım Adım Çözüm

1
Analyze the bootstrapping latency and scaling behavior.
Identify that the 6 minutes6\text{ minutes} bootstrapping delay causes connection drops during instant spikes, while the 180 second180\text{ second} cooldown causes redundant instance launches because the cooldown is shorter than the bootstrap time.
To mitigate this, pre-initialized instances in a warm pool and a scaling policy warmup period greater than the bootstrap time (420 seconds>360 seconds420\text{ seconds} > 360\text{ seconds}) are needed.
2
Analyze the fault tolerance requirements for outbound internet traffic.
Determine that routing all traffic through a single NAT Gateway in us-east-1a creates a single point of failure.
Deploying a NAT Gateway in us-east-1b and configuring its route table prevents cross-AZ dependency, ensuring outbound connectivity remains active for us-east-1b during an outage in us-east-1a.
3
Evaluate the architectural options to select the correct pair.
Select the combination of a warm pool with Stopped instances and a high warmup value, alongside a secondary NAT Gateway deployed in the separate Availability Zone.
This combination addresses both the application startup performance and the network infrastructure fault tolerance requirements.

Anahtar Kavram

Auto Scaling Warm Pools, Scaling Warmup Alignment, and Multi-AZ NAT Gateway Redundancy
Bu soruyu puanla