How can the Administrator troubleshoot the application without triggering the scaling process?
Suspend the scaling process before troubleshooting.
Delete the Auto Scaling group and recreate it when troubleshooting is complete.
Remove impacted instances from the Application Load Balancer.
Create a scale down trigger when the CPUUtilization instance metric is at 70%.
Explanations:
Suspending the scaling process prevents new instances from being launched or terminated, allowing troubleshooting without triggering additional scaling.
Deleting the Auto Scaling group would remove all instances, disrupting the application. Re-creation is unnecessary and doesn’t aid in troubleshooting.
Removing instances from the ALB may reduce load but does not address scaling triggers or prevent new instances from launching during troubleshooting.
Adding a scale-down trigger at 70% does not prevent scaling out at 75%; it only adds complexity and may not address the root cause of aggressive scaling.
If I’m not mistaken, the answer is:
Suspend the scaling process before troubleshooting.