A SysOps Administrator is running an automatically scaled application behind an Application Load Balancer. Scaling out is triggered when the CPUUtilization instance metric is more than 75% across the Auto Scaling group. The Administrator noticed aggressive scaling out. Developers suspect an application memory leak that is causing aggressive garbage collection cycles. How can the Administrator troubleshoot the application without triggering the scaling process?

Topic #: - All AWS-SysOps Questions

A. Suspend the scaling process before troubleshooting.
B. Delete the Auto Scaling group and recreate it when troubleshooting is complete.
C. Remove impacted instances from the Application Load Balancer.
D. Create a scale down trigger when the CPUUtilization instance metric is at 70%.

- Awsexamhub website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Suggested Answer:

Share this post

Join the Discussion