A company has an application that uses Amazon ElastiCache for Memcached to cache query responses to improve latency. However, the application's users are reporting slow response times. A SysOps admini

Question

Options

• AFlush the contents of ElastiCache for Memcached.
• BIncrease the ConnectionOverhead parameter value.
• CIncrease the number of nodes in the cluster.
• DIncrease the size of the nodes in the cluster.
• EDecrease the number of nodes in the cluster.

• A
  7% (4)
• B
  11% (7)
• C
  79% (48)
• E
  3% (2)

Explanation

ElastiCache Memcached Evictions Explanation

High eviction metrics in ElastiCache for Memcached indicate that the cache is running out of memory, forcing it to remove existing cached items to make room for new ones - this directly causes the slow response times users experience. Adding more nodes (C) distributes the cached data across additional nodes, increasing total cluster memory, while increasing node size (D) provides more memory per node; both solutions reduce memory pressure and lower evictions.

Why the distractors are wrong:

• (A) Flushing the cache would worsen performance by clearing all cached data, forcing more database queries
• (B) Increasing ConnectionOverhead reduces the memory available for caching (it reserves memory for connections), which would actually increase evictions
• (E) Decreasing nodes reduces total cache capacity, making evictions significantly worse

Memory Tip

Think of evictions like an overfull parking lot - cars (data) are being forced out because there's no space. You fix this by either adding more parking lots (more nodes) or building bigger parking structures (larger nodes). Never shrink the lot or remove cars already parked!

No community discussion yet for this question.