AWS Certified SysOps Administrator – Associate (legacy) — Question 771

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?

Answer options

• 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%.

Correct answer: A

Explanation

Suspending the scaling processes of an Auto Scaling group allows administrators to perform manual troubleshooting on the instances without triggering automatic scaling activities like launching or terminating instances. Deleting the Auto Scaling group would destroy the active environment needed for debugging, while removing instances from the load balancer or adjusting scale-down thresholds does not stop the Auto Scaling group from reacting to the high CPU utilization metric.