Examkin

Soru

Zorluk: OrtaImplementing Auto Scaling and Fault Tolerance

A company operates an online multiplayer game matchmaking service. The matchmaking application runs on Amazon EC2 instances in an Auto Scaling group (ASG) behind an Application Load Balancer. The application has a complex initialization process that takes about 10 minutes to load static assets and establish connections to external databases. During sudden peaks of player logins, the ASG scales out, but the newly launched instances take 10 minutes before they can process requests. During this initialization window, the target tracking policy launches multiple redundant batches of instances, leading to excessive resource provisioning and increased costs. Which configuration change will prevent the Auto Scaling group from launching unnecessary instances during the initialization period?

  1. Configure the target tracking scaling policy and increase the instance warmup time to match the application's 10-minute initialization period.Cevap
  2. B
    Decrease the scaling policy's cooldown period to allow the Auto Scaling group to respond faster to subsequent traffic demands.
  3. C
    Contact AWS Support to pre-warm the Application Load Balancer to handle the sudden burst of incoming matchmaking requests.
  4. D
    Place a single NAT Gateway in one of the public subnets to consolidate outbound traffic to the database and reduce initialization latency.

Cevap

Configure the target tracking scaling policy and increase the instance warmup time to match the application's 10-minute initialization period.
Configuring the target tracking scaling policy and increasing the instance warmup time to match the 10-minute initialization period ensures that the Auto Scaling group does not launch additional instances while the current batch is still bootstrapping. During the warmup period, the instances do not contribute to the scaling metric, preventing the policy from executing redundant scale-out actions.

Adım Adım Çözüm

1
Analyze the application behavior and resource provisioning pattern during scaling events.
The application requires a 10-minute bootstrap/initialization phase before it can serve traffic, but the Auto Scaling group's target tracking policy triggers subsequent scale-outs before the initial new instances start contributing to metric reduction.
This shows that the target tracking policy is evaluating the metric without factoring in the capacity of the instances that are currently launching and bootstrapping.
2
Identify the configuration parameter that controls how long the Auto Scaling group waits before newly launched instances contribute to the scaling metric.
The instance warmup parameter (specifically the 'Estimated Instance Warmup' for target tracking scaling policies) determines this duration.
Setting the warmup time to 10 minutes ensures that instances currently in the bootstrap phase are not counted as active capacity, and the scaling policy will not initiate further scale-outs based on outdated metrics until the warmup period expires.

Anahtar Kavram

Auto Scaling Instance Warmup Configuration
Bu soruyu puanla

Konular

Implementing Auto Scaling and Fault Tolerance