SOA-C03 · Question #158
A SysOps administrator monitors and maintains the availability of resources in an AWS environment. The SysOps administrator notices that the CPU utilization of an Amazon EC2 instance that runs web…
The correct answer is D. Set up an Auto Scaling group with an Amazon CloudWatch alarm that triggers a scaling policy to. The requirement is to fix performance degradation from predictable peak CPU load without service disruptions. The most reliable and operationally standard approach is horizontal scaling with an Auto Scaling group driven by CloudWatch metrics/alarms (or target tracking)…
Question
A SysOps administrator monitors and maintains the availability of resources in an AWS environment. The SysOps administrator notices that the CPU utilization of an Amazon EC2 instance that runs web server software peaks above 80% at various times during each day. The CPU spikes correlate with peak daily loads. The high CPU load has resulted in performance issues for customers. The SysOps administrator needs to resolve the system performance issue without causing any service disruptions. Which solution will meet these requirements?
Options
- AConfigure an Amazon CloudWatch alarm that invokes an AWS Systems Manager Automation
- BConfigure an AWS Systems Manager Automation runbook to run a script that automatically
- CConfigure an Amazon EventBridge rule that invokes an AWS Systems Manager Automation
- DSet up an Auto Scaling group with an Amazon CloudWatch alarm that triggers a scaling policy to
How the community answered
(47 responses)- A2% (1)
- B4% (2)
- C11% (5)
- D83% (39)
Explanation
The requirement is to fix performance degradation from predictable peak CPU load without service disruptions. The most reliable and operationally standard approach is horizontal scaling with an Auto Scaling group driven by CloudWatch metrics/alarms (or target tracking). Launching additional instances and distributing traffic (typically behind a load balancer) increases capacity while keeping existing instances serving requests--no reboot or stop/start required. Option D meets the requirement because Auto Scaling can add capacity when CPU exceeds a threshold and remove capacity when demand falls. This improves performance during peak periods and maintains availability. It is also operationally efficient: scaling actions are automated, consistent, and can be tuned with cooldowns/health checks.
Topics
Community Discussion
No community discussion yet for this question.