Which remediation steps should be taken to resolve this issue?
(Choose two.)
Add a larger Amazon EBS volume to the ElastiCache cluster nodes
Add a load balancer to route traffic to the ElastiCache cluster
Add additional worker nodes to the ElastiCache cluster
Create an Auto Scaling group for the ElastiCache cluster
Vertically scale the ElastiCache cluster by changing the node type
Explanations:
Adding a larger Amazon EBS volume won’t directly address CPU utilization, as EBS volumes are for storage, not memory or CPU processing. Memcached primarily relies on memory for performance.
A load balancer is used to distribute traffic across multiple instances but does not reduce CPU utilization directly for Memcached. Memcached is a caching system that would benefit from scaling nodes, not load balancing.
Adding additional worker nodes (i.e., horizontal scaling) allows the ElastiCache cluster to distribute the load more effectively, which can help lower the CPU utilization on individual nodes.
ElastiCache does not support Auto Scaling groups, as it is a managed service with fixed nodes. You cannot use Auto Scaling to adjust the number of nodes automatically in ElastiCache.
Vertically scaling (changing to a larger node type) increases the CPU capacity of each node, which directly addresses high CPU utilization on the current nodes. This is a valid remediation step.
I measure that the answer is:
Add additional worker nodes to the ElastiCache cluster