Which scaling strategy should a solutions architect recommend to meet these requirements?
Implement dynamic scaling with step scaling based on average CPU utilization from the EC2 instances.
Enable predictive scaling to forecast and scale. Configure dynamic scaling with target tracking
Create an automated scheduled scaling action based on the traffic patterns of the web application.
Set up a simple scaling policy. Increase the cooldown period based on the EC2 instance startup time.
Explanations:
Step scaling adjusts capacity based on thresholds, but it does not account for historical trends or forecasting. It is not suitable for predicting and adapting to both live changes and forecasted workloads.
Predictive scaling forecasts future demand and dynamically scales resources. Target tracking automatically adjusts capacity to meet a defined metric, providing an optimal solution for both historical trends and real-time utilization changes.
Scheduled scaling is static and does not adapt to real-time utilization or forecasted demand. It would not respond effectively to both live changes and future workload trends.
Simple scaling with a cooldown period is based on predefined policies and does not take into account historical trends or predictive scaling for future demand. It may result in inefficiencies for handling variable traffic patterns.