Topic 1 Question 336
ASysOps administrator configures an application to run on Amazon EC2 instances behind an Application Load Balancer (ALB) in a simple scaling Auto Scaling group with the default settings. The Auto Scaling group is configured to use the RequestCountPerTarget metric for scaling. The SysOps administrator notices that the RequestCountPerTarget metric exceeded the specified limit twice in 180 seconds.
How will the number of EC2 instances in this Auto Scaling group be affected in this scenario?
The Auto Scaling group will launch an additional EC2 instance every time the RequestCountPerTarget metric exceeds the predefined limit.
The Auto Scaling group will launch one EC2 instance and will wait for the default cooldown period before launching another instance.
The Auto Scaling group will send an alert to the ALB to rebalance the traffic and not add new EC2 instances until the load is normalized.
The Auto Scaling group will try to distribute the traffic among all EC2 instances before launching another instance.
ユーザの投票
コメント(3)
- 正解だと思う選択肢: B
Simple Scaling policy "DefaultCooldown" = 300 seconds https://docs.aws.amazon.com/autoscaling/ec2/userguide/consolidated-view-of-warm-up-and-cooldown-settings.html
👍 4Gomer2023/06/16 B
When the RequestCountPerTarget metric exceeds the specified limit, the Auto Scaling group will launch an additional EC2 instance to handle the increased load. However, after launching an instance, the Auto Scaling group will wait for the default cooldown period before launching another instance. The cooldown period is a configurable setting that helps ensure that the Auto Scaling group doesn’t launch or terminate additional instances before the previous scaling activity takes effect.
👍 2[Removed]2023/07/09- 正解だと思う選択肢: B
BBBB....
👍 2Christina6662023/07/28
シャッフルモード