Which solution will configure the development environment MOST cost-effectively?
Reconfigure the target group in the development environment to have only one EC2 instance as a target.
Change the ALB balancing algorithm to least outstanding requests.
Reduce the size of the EC2 instances in both environments.
Reduce the maximum number of EC2 instances in the development environment’s Auto Scaling group.
Explanations:
Reducing the target group to one EC2 instance may lead to limited availability and scaling issues, which isn’t optimal for cost efficiency in the development environment.
Changing the ALB balancing algorithm does not address cost optimization. The choice of algorithm affects traffic distribution but doesn’t directly reduce resource usage or cost.
Reducing the EC2 instance size in both environments may not be appropriate as the production environment requires handling high traffic. It could lead to performance degradation in production.
Reducing the maximum number of EC2 instances in the development environment’s Auto Scaling group directly lowers costs by ensuring fewer instances are launched, aligning with cost-effective usage.