Test your Caching Strategies knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is a common strategy for invalidating a cache entry immediately when the underlying data changes, rather than waiting for a TTL to expire?
In this round
What is a common strategy for invalidating a cache entry immediately when the underlying data changes, rather than waiting for a TTL to expire?
What is the difference between caching at the HTTP/CDN layer (e.g. `Cache-Control` headers) versus an in-memory application-level cache (e.g. Redis, Memcached)?
What does it mean for a caching strategy to trade "consistency" for "availability/performance," in the context of the wider distributed-systems consistency-vs-latency tradeoff?
What is a Content Delivery Network (CDN) cache, and why does it reduce latency for geographically distant users?
What is "cache warming" (or cache pre-loading)?
What is the risk of caching data that includes sensitive/private user information at a shared caching layer (like a CDN edge cache)?
Why is choosing a good cache key important, and what commonly goes wrong with poorly-designed cache keys?
What is a Time-To-Live (TTL) in caching?
Why can caching introduce consistency bugs in a distributed system with multiple app servers, each with its own local (in-process) cache?
What is an LRU (Least Recently Used) eviction policy?
What is the "thundering herd" (or "cache stampede") problem?
What is "negative caching," and what risk does it carry if misused?