Your company uses Amazon ElastiCache for Memcached as a cache solution for a new web application. A feature was deployed last week. Since then, the CloudWatch alarm has been triggered for the “Evictions” metric. It looks like the cache has evicted a large number of items to allow space for new writes. The function of the new feature is working as expected. Which action would you take to address the CloudWatch alarm? (Select TWO.)

Answer options:

A.Scale up the Memcached node by using a larger node type.
B.Increase the CloudWatch alarm threshold.
C.Scale out ElastiCache for Memcached by adding more nodes.
D.Change the ElastiCache cluster to Redis.
E.Rollback the application.

Correct Answers: A and C
Option A is CORRECT because the ElastiCache cluster has an ongoing performance issue. Scaling up the node can allocate more resources to address the problem.
Option B is incorrect because this option does not resolve the performance issue of the cache. The evicting of items still exists, and the application is being impacted.
Option C is CORRECT because allocating more nodes can decrease the number of cache evictions and improve the application performance.
Option D is incorrect because changing the cache engine requires lots of effort and is unnecessary for the question. Besides, ElastiCache for Redis cannot be used for certain circumstances.
Option E is incorrect because the CloudWatch alarm indicates a performance issue of the cache, and the question does not mention any software issue of the new feature. There is no need to roll back the application.
References:
https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/CacheMetrics.WhichShouldIMonitor.html#metrics-evictions
https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/CacheMetrics.Memcached.html