How should the scaling be changed to address the staff complaints and keep costs to a minimum?
A company runs an internal browser-based application The application runs on Amazon EC2 instances behind an Application Load Balancer The instances run in an Amazon EC2 Auto Scaling group across multiple Availability Zones The Auto Scaling group scales up to 20 instances during work hours, but scales down to 2 instances overnight Staff are complaining that the application is very slow when the day begins, although it runs well by mid-morning.
How should the scaling be changed to address the staff complaints and keep costs to a minimum?
A . Implement a scheduled action that sets the desired capacity to 20 shortly before the office opens
B . Implement a step scaling action triggered at a lower CPU threshold, and decrease the cooldown period.
C . Implement a target tracking action triggered at a lower CPU threshold and decrease the cooldown period
D . Implement a scheduled action that sets the minimum and maximum capacity to 20 shortly before the office opens
Answer: A
Explanation:
Reference: https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html
Latest SAA-C02 Dumps Valid Version with 230 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund