Back to Elastic Load Balancing (ELB)

ELB Auto Scaling

5 minutes 5 Questions

Auto Scaling is a feature that automatically adjusts the number of registered instances in an Elastic Load Balancer target group based on real-time demand, ensuring optimal workload distribution and availability. It supports both scale-out and scale-in operations, increasing or decreasing the numbe…

Test mode:
Start practice test
AWS Certified Solutions Architect - ELB Auto Scaling Example Questions

Test your knowledge of ELB Auto Scaling

Question 1

You have a web application running on EC2 instances in an Auto Scaling group (ASG) with an attached Classic Load Balancer (CLB). The instances are taking longer to provision, leading to slow scaling. What would be the BEST way to speed up scaling?

Correct Answer: Use Amazon Machine Images (AMIs) with the application pre-installed.

Using AMIs with the application pre-installed will decrease the time required for instance provisioning, allowing faster scaling. Switching to an ALB from a CLB doesn't affect scaling. Enabling multi-AZ deployments and termination protection don't address the root cause of the problem. Scheduled scaling can be helpful, but it may not address rapid scaling needs. Reducing Desired Capacity contradicts the need for scaling.

Question 2

A web application is deployed across two availability zones using an Application Load Balancer (ALB) and Auto Scaling groups. The ALB latency suddenly increases, causing client errors. What is the BEST way to resolve this issue?

Correct Answer: Enable Sticky Sessions on the ALB to bind user sessions to specific instances.

Enabling Sticky Sessions on the ALB helps to bind user sessions to specific instances, reducing latency and session-related errors. Switching to a Network Load Balancer wouldn't help, as it does not support sticky sessions. Decreasing the health check interval would not resolve the latency issue. Migrating the application to a single availability zone can compromise fault tolerance. Increasing the idle timeout value and using SSL offloading do not address the root cause of the problem.

Question 3

An application is running on EC2 instances in an Auto Scaling group with a Classic Load Balancer (CLB). A new version of the application has been developed. What would be the BEST method to deploy the new version without causing downtime?

Correct Answer: Use a Blue/Green deployment strategy with two Auto Scaling groups.

A Blue/Green deployment strategy with two Auto Scaling groups allows the new version to be tested before switching traffic, ensuring zero downtime. Terminating instances and launching new ones can cause downtime. Changing the instance type or switching to an ALB doesn't address the requirement for zero downtime. Deploying the new version to all instances simultaneously can cause issues and potential downtime. Scheduled scaling isn't relevant to this scenario.

More ELB Auto Scaling questions
15 questions (total)
Start 15 question test