SOA-C02 · Question #347
A SysOps administrator is testing an application mat is hosted on five Amazon EC2 instances. The instances run in an Auto Scaling group behind an Application Load Balancer (ALB) High CPU utilization d
The correct answer is D. Suspend the Launch and Terminate process types.. You can put an instance that is in the InService state into the Standby state, update or troubleshoot the instance, and then return the instance to service. Instances that are on standby are still part of the Auto Scaling group, but they do not actively handle load balancer traff
Question
A SysOps administrator is testing an application mat is hosted on five Amazon EC2 instances. The instances run in an Auto Scaling group behind an Application Load Balancer (ALB) High CPU utilization during load testing is causing the Auto Scaling group to scale out. The SysOps administrator must troubleshoot to find the root cause of the high CPU utilization before the Auto Scaling group scales out. Which action should the SysOps administrator take to meet these requirements?
Options
- AEnable instance scale-in protection.
- BPlace the instance into the Standby stale.
- CRemove the listener from the ALB
- DSuspend the Launch and Terminate process types.
How the community answered
(39 responses)- A13% (5)
- B3% (1)
- C5% (2)
- D79% (31)
Explanation
You can put an instance that is in the InService state into the Standby state, update or troubleshoot the instance, and then return the instance to service. Instances that are on standby are still part of the Auto Scaling group, but they do not actively handle load balancer traffic. https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-enter-exit-standby.html
Topics
Community Discussion
No community discussion yet for this question.