Auto Scaling

A user is trying to setup a scheduled scaling activity using Auto Scaling. The user wants to setup the recurring schedule. Which of the below mentioned parameters is not required in this case?

• Maximum size
• Auto Scaling group name
• End time
• Recurrence value

A user has configured Auto Scaling with 3 instances. The user had created a new AMI after updating one of the instances. If the user wants to terminate two specific instances to ensure that Auto Scaling launches an instances with the new launch configuration, which command should he run?

• as-delete-instance-in-auto-scaling-group �no-decrement-desired-capacity
• as-terminate-instance-in-auto-scaling-group �update-desired-capacity
• as-terminate-instance-in-auto-scaling-group �decrement-desired-capacity
• as-terminate-instance-in-auto-scaling-group �no-decrement-desired-capacity

A user is planning to scale up an application by 8 AM and scale down by 7 PM daily using Auto Scaling. What should the user do in this case?

• Setup the scaling policy to scale up and down based on the CloudWatch alarms
• User should increase the desired capacity at 8 AM and decrease it by 7 PM manually
• User should setup a batch process which launches the EC2 instance at a specific time
• Setup scheduled actions to scale up or down at a specific time

An organization has setup Auto Scaling with ELB. Due to some manual error, one of the instances got rebooted. Thus, it failed the Auto Scaling health check. Auto Scaling has marked it for replacement. How can the system admin ensure that the instance does not get terminated?

• 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

A user has configured Auto Scaling with the minimum capacity as 2 and the desired capacity as 2. The user is trying to terminate one of the existing instance with the command: as-terminate-instance-in-auto-scaling-group �decrement-desired-capacity. What will Auto Scaling do in this scenario?

• Terminates the instance and does not launch a new instance
• Terminates the instance and updates the desired capacity to 1
• Terminates the instance and updates the desired capacity &�minimum size to 1
• Throws an error

An organization has configured Auto Scaling for hosting their application. The system admin wants to understand the Auto Scaling health check process. If the instance is unhealthy, Auto Scaling launches an instance and terminates the unhealthy instance. What is the order execution?

• Auto Scaling launches a new instance first and then terminates the unhealthy instance
• Auto Scaling performs the launch and terminate processes in a random order
• Auto Scaling launches and terminates the instances simultaneously
• Auto Scaling terminates the instance first and then launches a new instance

A user has configured ELB with Auto Scaling. The user suspended the Auto Scaling terminate process only for a while. What will happen to the availability zone rebalancing process (AZRebalance) during this period?

• 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

An organization has configured Auto Scaling with ELB. There is a memory issue in the application which is causing CPU utilization to go above 90%. The higher CPU usage triggers an event for Auto Scaling as per the scaling policy. If the user wants to find the root cause inside the application without triggering a scaling activity, how can he achieve this?

• Stop the scaling process until research is completed
• It is not possible to find the root cause from that instance without triggering scaling
• Delete Auto Scaling until research is completed
• Suspend the scaling process until research is completed

A user has configured ELB with Auto Scaling. The user suspended the Auto Scaling Alarm Notification (which notifies Auto Scaling for CloudWatch alarms) process for a while. What will Auto Scaling do during this period?

• AWS will not receive the alarms from CloudWatch
• AWS will receive the alarms but will not execute the Auto Scaling policy
• Auto Scaling will execute the policy but it will not launch the instances until the process is resumed
• It is not possible to suspend the AlarmNotification process

. An organization has configured two single availability zones. The Auto Scaling groups are configured in separate zones. The user wants to merge the groups such that one group spans across multiple zones. How can the user configure this?

• Run the command as-join-auto-scaling-group to join the two groups
• Run the command as-update-auto-scaling-group to configure one group to span across zones and delete the other group
• Run the command as-copy-auto-scaling-group to join the two groups
• Run the command as-merge-auto-scaling-group to merge the groups