Multiple ChoiceBeginner 45s
Write-back cache risk
What is the primary durability risk of a write-back (write-behind) cache?
Options
- 1Reads served from the cache become strongly consistent, because the write path always updates the DB before returning
- 2The cache will always return stale data for any TTL-expired key, because write-back never refetches from the database
- 3Acknowledged writes still in the cache can be lost if the cache node crashes before flushing to the DB
- 4It requires the backing database to be sharded by cache key, else the cache cannot locate where a dirty entry is flushed
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.