You are developing a web application that uses Azure Cache for Redis. You anticipate that the cache will frequently fill and that you will need to evict keys. You must configure Azure Cache for…

Question

Options

• Anoeviction
• Ballkeys-lru
• Cvolatile-lru
• Dallkeys-random
• Evolatile-ttl
• Fvolatile-random

• A
  8% (3)
• B
  73% (29)
• D
  15% (6)
• E
  3% (1)
• F
  3% (1)

Explanation

B: The allkeys-lru policy evict keys by trying to remove the less recently used (LRU) keys first, in order to make space for the new data added. Use the allkeys-lru policy when you expect a power- law distribution in the popularity of your requests, that is, you expect that a subset of elements will be accessed far more often than the rest. C: volatile-lru: evict keys by trying to remove the less recently used (LRU) keys first, but only among keys that have an expire set, in order to make space for the new data added. Note: The allkeys-lru policy is more memory efficient since there is no need to set an expire for the key to be evicted under memory pressure. https://redis.io/topics/lru-cache

No community discussion yet for this question.