CLOUD COMPUTING
AUTOSCALING
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Auto Scaling will not launch or terminate any instances
|
|
|
Auto Scaling will allow the instances to grow more than the maximum size
|
|
|
Auto Scaling will keep launching instances till the maximum instance size
|
|
|
It is not possible to suspend the terminate process while keeping the launch active
|
Detailed explanation-1: -If the user suspends the Terminate process, the AZRebalance process can cause the Auto Scaling group to grow up to ten percent larger than the maximum size. This is because Auto Scaling allows groups to temporarily grow larger than the maximum size during rebalancing activities.
Detailed explanation-2: -If you detach instances from your Auto Scaling group, you put instances on standby, or you explicitly terminate instances and decrement the desired capacity, which prevents replacement instances from launching, the group can become unbalanced.
Detailed explanation-3: -If HANDLE PROCS=true, the following Auto Scaling events are suspended automatically during the deployment process: AZRebalance. AlarmNotification. ScheduledActions.
Detailed explanation-4: -Terminate instances that have the oldest launch template. With this policy, instances that use the noncurrent launch template are terminated first, followed by instances that use the oldest version of the current launch template.
Detailed explanation-5: -Open the Amazon EC2 console. In the navigation pane, under Auto Scaling, choose Auto Scaling Groups. Then, choose the instance’s group. Choose the Activity History view, and then choose the instance termination event. Note the Description and Cause for the instance termination event.