Your company runs a video analysis software that is available in both Free and Paid plans. To support the Free and Paid versions effectively, your company uses a spot pricing framework that does the bidding as per the subscription plan to ensure the availability of the spot instances and maintain the cost. The instances are running behind a load balancer created for the analysis job with the auto-scaling group attached to that. Paid subscription jobs are set to run into multiple availability zones to maintain high availability. The application using the spot engine adds the desired instances based on active jobs and terminates instances when the processing is completed. By looking at the CloudWatch logs, you noticed that sometimes the Auto Scaling launches new instances before terminating the old ones. What could the cause and the corresponding resolution for this issue?

Answer options:

A.Update the desired capacity of the Auto Scaling Group based on the number of active jobs.
B.Auto Scaling triggers the AZRebalance event if the number of instances in availability zones are not matching after terminating instances. Suspend the AZRebalance process of Auto Scaling to avoid the rebalancing.
C.Run all the instances into a single availability zone.
D.Adjust the min and max capacity of the Auto Scaling Group after the jobs are completed.

Correct Answer: B
Option A is INCORRECT because the desired capacity is meant to maintain a minimum number of instances in an Auto Scaling group.
Option B is CORRECT because suspending the AZRebalance will disable the instance balancing activity if the availability zones have a different number of instances.
Option C is INCORRECT for the current situation. If the Auto Scaling runs into a single availability zone, the AZRebalance event will not trigger. But at the same time, it will not be fault-tolerant against availability zone failures.
Option D is INCORRECT because the min/max count does not affect the availability zone rebalance process.