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?

Answer options:

A.Stop the scaling process until research is completed.
B.It is not possible to find the root cause from that instance without triggering scaling.
C.Delete the Auto Scaling group until research is completed.
D.Suspend the scaling process until research is completed.

Answer – D
In this scenario, the user wants to investigate the problem during the Auto Scaling process without triggering the scaling activity. For this, the user can leverage the suspend and resume option available on Auto Scaling.
Option A is incorrect because the scaling process needs not to be stopped. It can be suspended so that it can be resumed.
Option B is incorrect because scaling can be momentarily suspended until the investigation is completed.
Option C is incorrect because the Auto Scaling group is totally unnecessary in this scenario.
Option D is CORRECT because you can suspend and then resume one or more of the scaling processes for your Auto Scaling group, if you want to investigate a configuration problem or other issue with your web application and then make changes to your application without triggering the scaling processes.
For more information on suspending AutoScaling processes, please visit the link
http://docs.aws.amazon.com/autoscaling/latest/userguide/as-suspend-resume-processes.html