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
Explanations:
Stopping the scaling process would not allow for continued monitoring of the application’s performance and could lead to additional issues if the resource utilization increases beyond safe levels. Moreover, it may not provide insights into the application’s behavior during this period.
It is possible to find the root cause of the issue without triggering a scaling event by using monitoring tools and logs to analyze CPU utilization without scaling the instance. Techniques such as adjusting scaling policies or using CloudWatch alarms could help.
Deleting the Auto Scaling group would prevent any instances from being managed, leading to potential downtime or further issues with the application. This approach would hinder rather than help in diagnosing the root cause.
Suspending the scaling process allows the user to maintain the current instances without triggering new scaling activities. This way, they can analyze the application behavior and resource utilization without interruptions from the Auto Scaling policies.
If I’m correct, the answer is:
Suspend the scaling process until research is completed
As far as I can tell, the answer is:
Suspend the scaling process until research is completed