Q96 — AWS SAA-C03 Ch.11

Question 96 of 100 | ← Chapter 11

Q796. A company runs a three-tier web application in a VPC across multiple Availability Zones. Amazon EC2 instances run in an Auto Scaling group for the application tier.The company needs to make an automated scaling plan that will analyze each resource's daily and weekly historical workload trends. The configuration must scale resources appropriately according to both the forecast and live changes in utilization.Which scaling strategy should a solutions architect recommend to meet these requirements?

Correct Answer: B. Enable predictive scaling to forecast and scale. Configure dynamic scaling with target tracking

Explanation

To meet the requirements of analyzing historical workload trends, forecasting, and scaling resources appropriately based on both forecast and live changes in utilization for a three-tier web application running in a VPC with EC2 instances in an Auto Scaling group, the recommended scaling strategy is:B. Enable predictive scaling to forecast and scale. Configure dynamic scaling with target tracking.Enabling predictive scaling allows you to forecast the capacity needs of your application based on historical workload patterns. This feature uses machine learning algorithms to analyze historical data and automatically creates scaling plans that include the appropriate scaling actions to meet predicted demand.By configuring dynamic scaling with target tracking, you can set a target value for a specific metric, such as CPU utilization, and let Auto Scaling adjust the resource capacity to maintain that target value. This approach ensures that resources are scaled up or down based on both the forecasted workload and live changes in utilization.Here's why the other options are not the best fit for the given requirements:A. Implementing dynamic scaling with step scaling based on average CPU utilization: While dynamic scaling with step scaling is a valid approach to scale resources based on CPU utilization, it does not take into account the requirement of analyzing historical workload trends and forecasting.C. Creating an automated scheduled scaling action based on traffic patterns: Scheduled scaling is useful for predictable workload patterns, but it does not address the requirement of analyzing historical trends and adapting to live changes in utilization.D. Setting up a simple scaling policy and increasing the cooldown period based on EC2 instance startup time: This option does not consider the requirement of analyzing historical workload trends and forecasting. Increasing the cooldown period based on the instance startup time is not directly related to scaling based on workload demands.Therefore, the recommended scaling strategy that meets the requirements of analyzing historical workload trends, forecasting, and scaling resources appropriately based on both forecast and live changes in utilization is:B. Enable predictive scaling to forecast and scale. Configure dynamic scaling with target tracking.