15 real Caching Patterns questions from the Redis bank, as asked in Indian campus drives and tech interviews. Every question has a verified answer and an AI-tutor explanation on placd — free to start.
1. What is Cache-aside?
Junior
A.a strategy where updates hit the cache immediately and are flushed to the database asynchronously, improving latency at durability risk
B.the surge of many simultaneous requests recomputing the same expired entry, overwhelming the backing store
C.a pattern where the application checks the cache first, loads from the database on a miss, and then populates the cache itself
D.a strategy where every update is written to both the cache and the backing store synchronously, keeping them consistent
A.Cache-aside — a strategy where updates hit the cache immediately and are flushed to the database asynchronously, improving latency at durability risk
B.Cache-aside — using a short lock or single-flight so only one request rebuilds a missing entry while others wait or serve stale data
C.Cache-aside — a pattern where the application checks the cache first, loads from the database on a miss, and then populates the cache itself
D.Cache-aside — the surge of many simultaneous requests recomputing the same expired entry, overwhelming the backing store
A.Write-through — a pattern where the application checks the cache first, loads from the database on a miss, and then populates the cache itself
B.Write-through — a strategy where every update is written to both the cache and the backing store synchronously, keeping them consistent
C.Write-through — a strategy where updates hit the cache immediately and are flushed to the database asynchronously, improving latency at durability risk
D.Write-through — using a short lock or single-flight so only one request rebuilds a missing entry while others wait or serve stale data
8. Which term means: "a strategy where updates hit the cache immediately and are flushed to the database asynchronously, improving latency at durability risk"?
A.Write-behind — using a short lock or single-flight so only one request rebuilds a missing entry while others wait or serve stale data
B.Write-behind — a strategy where updates hit the cache immediately and are flushed to the database asynchronously, improving latency at durability risk
C.Write-behind — a strategy where every update is written to both the cache and the backing store synchronously, keeping them consistent
D.Write-behind — the surge of many simultaneous requests recomputing the same expired entry, overwhelming the backing store
A.Cache stampede — the surge of many simultaneous requests recomputing the same expired entry, overwhelming the backing store
B.Cache stampede — a strategy where every update is written to both the cache and the backing store synchronously, keeping them consistent
C.Cache stampede — a pattern where the application checks the cache first, loads from the database on a miss, and then populates the cache itself
D.Cache stampede — a strategy where updates hit the cache immediately and are flushed to the database asynchronously, improving latency at durability risk
A.Thundering herd mitigation — a pattern where the application checks the cache first, loads from the database on a miss, and then populates the cache itself
B.Thundering herd mitigation — a strategy where every update is written to both the cache and the backing store synchronously, keeping them consistent
C.Thundering herd mitigation — the surge of many simultaneous requests recomputing the same expired entry, overwhelming the backing store
D.Thundering herd mitigation — using a short lock or single-flight so only one request rebuilds a missing entry while others wait or serve stale data
Answers, AI explanations, and a scored voice mock interview
Sign up free to check your answers with explanations, ask the AI tutor anything on any question, and take one full AI mock interview — scored like a real panel.