codejump

Caching Strategies — Series 2

Preview — 3 of 10 questions

An app calls only cache.get(id); the cache library fetches missing records from the database. What changes compared with cache-aside?

AThe database is removed from the read path even on misses.
BThe cache layer owns miss loading.
CEvery write becomes a distributed transaction across all caches.
DCached values become permanently fresh without invalidation.

A deployment starts 200 instances with empty caches. Each would preload the same million records. What is a safer warm-up strategy?

ARetry every failed preload immediately with more parallel workers.
BStart every full preload simultaneously before enabling health checks.
CDisable cache eviction until all million records are present.
DWarm a bounded hot subset gradually under a shared load budget.

A service caches user not found for ten minutes. A user is created one minute later. What must the design consider?

AIncrease its TTL so replicas have more time to converge.
BStore the new user under a random lookup key.
CKeep the negative entry because only successful results become stale.
DInvalidate the negative entry or accept a documented visibility delay.

Sign up free to play

Answer all 10 questions (7 more), see explanations for every answer, and track your score.