Q29 — AWS SAA-C03 Ch.15

Question 29 of 100 | ← Chapter 15

Q1129. A company hosts a public web application on AWS. The website has a three-tier architecture. The frontend web tier is comprised of Amazon EC2 instances in an Auto Scaling group.The application tier is a second Auto Scaling group. The database tier is an Amazon RDS database.The company has configured the Auto Scaling groups to handle the application's normal level of demand. During an unexpected spike in demand, the company notices a long delay in the startup time when the frontend and application layers scale out. The company needs to improve the scaling performance of the application without negatively affecting the user experience.Which solution will meet these requirements MOST cost-effectively?

• A. Decrease the minimum number of EC2 instances for both Auto Scaling groups. Increase the desired number of instances to meet the peak demand requirement.
• B. Configure the maximum number of instances for both Auto Scaling groups to be the number required to meet the peak demand. Create a warm pool. ✓
• C. Increase the maximum number of EC2 instances for both Auto Scaling groups to meet the normal demand requirement. Create a warm pool.
• D. Reconfigure both Auto Scaling groups to use a scheduled scaling policy. Increase the size of the EC2 instance types and the RDS instance types.

Correct Answer: B. Configure the maximum number of instances for both Auto Scaling groups to be the number required to meet the peak demand. Create a warm pool.

Explanation

The solution that will meet the requirements to improve the scaling performance of the application during unexpected spikes in demand, without negatively affecting user experience, is:B. Configure the maximum number of instances for both Auto Scaling groups to be the number required to meet the peak demand. Create a warm pool.Explanation:Warm Pool: A warm pool allows you to keep a set of pre-initialized instances ready to be quickly deployed. This significantly reduces the startup time compared to launching instances from scratch, which is critical during unexpected spikes in demand.Maximum Instances: By configuring the maximum number of instances to meet peak demand, you ensure that the Auto Scaling groups can respond quickly when demand increases, without having to wait for new instances to initialize fully.Why Other Options Are Not Suitable:A: Decreasing the minimum number of instances may lead to insufficient capacity during peak demand, increasing the risk of delays and negatively impacting user experience.C: While increasing the maximum number of instances and creating a warm pool is beneficial, simply increasing the maximum instances without ensuring they can handle peak demand might still lead to delays if the demand exceeds the available warm instances.D: Using scheduled scaling policies and increasing instance sizes does not address the immediate need for faster scaling during unexpected spikes and may lead to higher costs unnecessarily without improving responsiveness.Thus, option B provides the most effective and cost-efficient solution for improving the scaling performance of the application.