An ecommerce company uses Amazon ElastiCache (Redis OSS) for caching product queries. The CloudOps engineer observes a large number of cache evictions in Amazon CloudWatch metrics and needs to reduce

Question

Options

• AAdd another node to the ElastiCache cluster.
• BIncrease the ElastiCache TTL value.
• CDecrease the ElastiCache TTL value.
• DMigrate to a new ElastiCache cluster with larger nodes.

• A
  13% (2)
• C
  6% (1)
• D
  81% (13)

Explanation

According to the AWS Cloud Operations and ElastiCache documentation, cache evictions occur when the cache runs out of memory and must remove items to make space for new data. To reduce evictions and retain frequently accessed items, AWS recommends increasing the total available memory -- either by scaling up to larger node types or scaling out by adding shards/nodes. Migrating to a cluster with larger nodes is the simplest and most efficient solution because it immediately expands capacity without architectural changes. Adjusting TTL (Options B and C) controls expiration timing, not memory allocation. Adding a single node (Option A) may help, but redistributing data requires resharding, introducing more Thus, Option D provides the lowest operational overhead and ensures high cache hit rates by increasing total cache memory.

No community discussion yet for this question.