Examkin

Soru

Zorluk: KolayImplementing Auto Scaling and Fault Tolerance

A company runs a batch processing worker fleet of Amazon EC2 instances managed by an Auto Scaling group. The worker instances require 66 minutes to complete their initialization and setup scripts before they are ready to process messages from an Amazon SQS queue. The current scaling policy uses a default cooldown period of 33 minutes. During sudden message volume increases, the Auto Scaling group repeatedly launches unnecessary additional instances before the newly created instances can begin processing messages. Which change should a Solutions Architect implement to optimize the scaling behavior and prevent over-provisioning?

  1. Increase the default cooldown period of the Auto Scaling group to at least 66 minutes to match the initialization time of the instances.Cevap
  2. B
    Decrease the default cooldown period of the Auto Scaling group to 11 minute to allow scaling metrics to stabilize faster.
  3. C
    Submit a request to AWS Support to pre-warm the fronting Application Load Balancer to absorb the sudden demand spike.
  4. D
    Deploy a single NAT Gateway in a public subnet to accelerate the retrieval of setup dependencies for the instances.

Cevap

Increase the default cooldown period of the Auto Scaling group to at least 66 minutes to match the initialization time of the instances.
The correct option correctly identifies that the cooldown period must be at least as long as the initialization time of 66 minutes. This ensures that the Auto Scaling group does not launch additional instances in response to outdated scaling metrics while the newly launched instances are still bootstrapping.

Adım Adım Çözüm

1
Analyze the instance bootstrapping and initialization time relative to the scaling cooldown period.
Instances require 66 minutes to initialize, while the current cooldown period is set to 33 minutes.
This shows that the cooldown period is shorter than the bootstrapping time, which is the root cause of the redundant scale-out events.
2
Determine the required cooldown adjustment to prevent premature scaling actions.
The cooldown period must be set to at least 66 minutes.
By ensuring the cooldown period is equal to or greater than the 66-minute initialization time, the Auto Scaling group will not launch additional instances until the currently launching instances have started processing SQS messages and influenced the metrics.

Anahtar Kavram

Auto Scaling Cooldown Configuration
Tahmini Süre:1m 0s
Bu soruyu puanla

Konular

Implementing Auto Scaling and Fault Tolerance