Which combination of actions should the solutions architect take to ensure that the system can scale to meet demand?
(Choose two.)
Use AWS Auto Scaling to adjust the ALB capacity based on request rate.
Use AWS Auto Scaling to scale the capacity of the VPC internet gateway.
Launch the EC2 instances in multiple AWS Regions to distribute the load across Regions.
Use a target tracking scaling policy to scale the Auto Scaling group based on instance CPU utilization.
Use scheduled scaling to change the Auto Scaling group minimum, maximum, and desired capacity to zero for weekends. Revert to the default values at the start of the week.
Explanations:
AWS Auto Scaling does not adjust the ALB capacity directly; it scales the EC2 instances based on metrics. The ALB itself scales automatically and does not need specific scaling actions.
The VPC internet gateway has a fixed capacity and does not need scaling. AWS Auto Scaling cannot adjust the capacity of the internet gateway.
While launching EC2 instances in multiple regions can help distribute load, it is not necessary for this scenario where the demand can be managed through Auto Scaling in a single region.
A target tracking scaling policy based on instance CPU utilization allows the Auto Scaling group to dynamically adjust the number of EC2 instances in response to actual demand, ensuring optimal resource use.
Scheduled scaling allows for setting the Auto Scaling group to have zero instances during weekends, preventing unnecessary costs and scaling back up at the start of the week when demand increases.
I rate that the answer is:
Use a target tracking scaling policy to scale the Auto Scaling group based on instance CPU utilization.
In my opinion, the answer is:
Use a target tracking scaling policy to scale the Auto Scaling group based on instance CPU utilization.