CLOUD COMPUTING
AUTOSCALING
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
Update the Auto Scaling group to ignore the instance reboot event
|
|
It is not possible to change the status once it is marked for replacement
|
|
Manually add that instance to the Auto Scaling group after reboot to avoid replacement
|
|
Change the health of the instance to healthy using the Auto Scaling commands
|
Detailed explanation-1: -The default health checks for an Auto Scaling group are EC2 health checks only. If an instance fails these health checks, it is marked unhealthy and is terminated while Amazon EC2 Auto Scaling launches a new replacement instance. For more information, see Health checks for Auto Scaling instances.
Detailed explanation-2: -An instance might fail the Elastic Load Balancing health check because an application running on the instance has issues that cause the load balancer to consider the instance out of service.
Detailed explanation-3: -When Amazon EC2 Auto Scaling determines that an InService instance is unhealthy, it terminates the instance while it launches a new replacement instance. The new instance launches using the current settings of the Auto Scaling group and its associated launch template or launch configuration.
Detailed explanation-4: -Elastic Load Balancing types Elastic Load Balancing provides four types of load balancers that can be used with your Auto Scaling group: Application Load Balancers, Network Load Balancers, Gateway Load Balancers, and Classic Load Balancers.