A company runs multiple web applications on Amazon EC2 instances behind a single Application Load Balancer (ALB). The application experiences unpredictable traffic spikes throughout each day. The…

Question

Options

• AUse EC2 instances in an Auto Scaling group. Configure the ALB and Auto Scaling group to use a
• BUse EC2 Reserved Instances in an Auto Scaling group. Configure the Auto Scaling group to use
• CUse EC2 Spot Instances in an Auto Scaling group. Configure the Auto Scaling group to use a
• DUse EC2 Reserved Instances in an Auto Scaling group. Replace the ALB with a Network Load

• A
  81% (17)
• B
  5% (1)
• C
  5% (1)
• D
  10% (2)

Explanation

AWS recommends Auto Scaling with dynamic scaling policies to handle unpredictable workload spikes. Target tracking scaling policies automatically adjust capacity based on defined metrics such as average CPU utilization or request count per target. This approach ensures applications maintain responsiveness without overprovisioning. Scheduled scaling (options B and C) is only effective when traffic patterns are predictable, which is not the case here. Reserved Instances or Spot Instances also do not address sudden demand changes effectively. Replacing the ALB with an NLB (D) does not solve latency caused by EC2 instance capacity. Therefore, using EC2 instances in an Auto Scaling group with a target tracking scaling policy is the most effective and cost-efficient solution for unpredictable, short-lived traffic spikes.

No community discussion yet for this question.