How should the SysOps administrator configure the scaling of the EC2 instances to meet these requirements?
Create a target tracking scaling policy that runs when the CPU utilization is higher than 90%.
Create a target tracking scaling policy that runs when the CPU utilization is higher than 50%. Create a scheduled scaling policy that ensures that the fleet is available at 09:00. Create a second scheduled scaling policy that scales in the fleet at 17:00.
Set the Auto Scaling group to start with 2 instances by setting the desired instances, maximum instances, and minimum instances to 2. Create a scheduled scaling policy that ensures that the fleet is available at 09:00.
Create a scheduled scaling policy that ensures that the fleet is available at 09:00. Create a second scheduled scaling policy that scales in the fleet at 17:00.
Explanations:
A target tracking scaling policy set to trigger when CPU utilization exceeds 90% is not suitable for maintaining 50% CPU availability. This would only scale the instances when CPU usage is too high, not ensuring 50% CPU is available for bursts.
This option includes a target tracking scaling policy to maintain 50% CPU utilization, ensuring that the fleet can scale based on the load. The scheduled scaling policies scale the fleet at 09:00 and scale it down at 17:00, ensuring the fleet size accommodates the increased load during working hours.
Starting with only 2 instances and scaling based on a single scheduled scaling policy at 09:00 does not meet the requirement to accommodate traffic bursts and ensure 50% CPU availability.
Although scheduled scaling at 09:00 and 17:00 addresses the time-based scaling, there is no mechanism to ensure 50% CPU availability during peak times. This solution does not account for the fluctuating load during the day.