Instance Behavior during Suspension Period

Answer - C.

If you suspend AddToLoadBalancer, Auto Scaling launches the instances but does not add them to the load balancer or target group.

If you resume the AddToLoadBalancer process, Auto Scaling resumes adding instances to the load balancer or target group when they are launched.

However, Auto Scaling does not add the instances that were launched while this process was suspended.

You must register those instances manually.

For more information on the Suspension and Resumption process, please visit the below URL:

When an Auto Scaling group launches new instances, it adds them to the Elastic Load Balancer (ELB) as part of the AddToLoadBalancer process. If you decide to suspend this process for a short period of time, the following will happen to the instances launched during that suspension period:

B. Auto Scaling will not launch the instances during this period because of the suspension.

The AddToLoadBalancer process is a critical component of Auto Scaling, and suspending it will stop Auto Scaling from launching new instances until the suspension is lifted. This means that any instances that were launched during the suspension period will not be added to the ELB, and they will not be available to handle requests until they are registered.

A. The instances will be registered with ELB once the process has resumed.

Once the suspension is lifted and the AddToLoadBalancer process resumes, any new instances launched by Auto Scaling will be added to the ELB automatically. However, the instances launched during the suspension period will not be added to the ELB until they are manually registered.

D. You must manually register when the process is resumed.

To register the instances with the ELB, you can either do it manually or use an AWS Lambda function to automate the process. Once the instances are registered with the ELB, they will be available to handle requests.

C. The instances will not be registered with EL.

This is partially true. The instances will not be registered with the ELB automatically during the suspension period, but they can be registered manually once the suspension is lifted.

E. It is not possible to suspend the AddToLoadBalancer process.

This is not true. You can suspend the AddToLoadBalancer process if you need to perform maintenance on the ELB or make changes to the Auto Scaling group configuration that require the suspension of the process.

In summary, if you decide to suspend the AddToLoadBalancer process, Auto Scaling will not launch new instances during that period. Any instances launched during the suspension period will not be added to the ELB automatically, and you will need to register them manually once the suspension is lifted.