18 real Caching Patterns questions from the Caching 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 pattern where the application checks the store first and loads from the database on a miss, then populates the store
B.a pattern that synchronously updates the store and the database together on every write, keeping both consistent at the cost of write latency
C.a pattern that updates the fast store immediately and persists to the database asynchronously later, improving write throughput but risking data loss
D.a pattern that proactively reloads soon-to-expire entries before they are requested, hiding refresh latency from users
A.Cache-aside — a pattern where the cache itself loads missing data from the backing store, so the application only ever talks to the cache
B.Cache-aside — populating a fast store only when data is first requested rather than ahead of time, so only accessed items consume memory
C.Cache-aside — a pattern where the application checks the store first and loads from the database on a miss, then populates the store
D.Cache-aside — a pattern that updates the fast store immediately and persists to the database asynchronously later, improving write throughput but risking data loss
A.a pattern that proactively reloads soon-to-expire entries before they are requested, hiding refresh latency from users
B.a pattern where the cache itself loads missing data from the backing store, so the application only ever talks to the cache
C.a pattern where the application checks the store first and loads from the database on a miss, then populates the store
D.a pattern that updates the fast store immediately and persists to the database asynchronously later, improving write throughput but risking data loss
8. Which term means: "a pattern that synchronously updates the store and the database together on every write, keeping both consistent at the cost of write latency"?
A.Write-through — a pattern where the application checks the store first and loads from the database on a miss, then populates the store
B.Write-through — a pattern that proactively reloads soon-to-expire entries before they are requested, hiding refresh latency from users
C.Write-through — a pattern that updates the fast store immediately and persists to the database asynchronously later, improving write throughput but risking data loss
D.Write-through — a pattern that synchronously updates the store and the database together on every write, keeping both consistent at the cost of write latency
A.a pattern where the application checks the store first and loads from the database on a miss, then populates the store
B.a pattern that proactively reloads soon-to-expire entries before they are requested, hiding refresh latency from users
C.a pattern where the cache itself loads missing data from the backing store, so the application only ever talks to the cache
D.a pattern that updates the fast store immediately and persists to the database asynchronously later, improving write throughput but risking data loss
11. Which term means: "a pattern that updates the fast store immediately and persists to the database asynchronously later, improving write throughput but risking data loss"?
A.Write-behind — a pattern that updates the fast store immediately and persists to the database asynchronously later, improving write throughput but risking data loss
B.Write-behind — a pattern where the cache itself loads missing data from the backing store, so the application only ever talks to the cache
C.Write-behind — populating a fast store only when data is first requested rather than ahead of time, so only accessed items consume memory
D.Write-behind — a pattern that synchronously updates the store and the database together on every write, keeping both consistent at the cost of write latency
A.a pattern where the cache itself loads missing data from the backing store, so the application only ever talks to the cache
B.a pattern where the application checks the store first and loads from the database on a miss, then populates the store
C.a pattern that proactively reloads soon-to-expire entries before they are requested, hiding refresh latency from users
D.a pattern that updates the fast store immediately and persists to the database asynchronously later, improving write throughput but risking data loss
A.Refresh-ahead — a pattern that proactively reloads soon-to-expire entries before they are requested, hiding refresh latency from users
B.Refresh-ahead — a pattern that synchronously updates the store and the database together on every write, keeping both consistent at the cost of write latency
C.Refresh-ahead — a pattern where the application checks the store first and loads from the database on a miss, then populates the store
D.Refresh-ahead — a pattern where the cache itself loads missing data from the backing store, so the application only ever talks to the cache
A.Lazy loading — a pattern that updates the fast store immediately and persists to the database asynchronously later, improving write throughput but risking data loss
B.Lazy loading — populating a fast store only when data is first requested rather than ahead of time, so only accessed items consume memory
C.Lazy loading — a pattern where the cache itself loads missing data from the backing store, so the application only ever talks to the cache
D.Lazy loading — a pattern that proactively reloads soon-to-expire entries before they are requested, hiding refresh latency from users
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.