Multiple ChoiceBeginner 45s
Read replica routing lag hazard
After a user writes their profile then immediately reads it, they see stale data. What is the most common cause and fix?
Options
- 1The write failed silently on the primary; retry with idempotency keys until a read confirms that the row was persisted
- 2The CDN cached an old profile; purge edge locations so the next read is forced back through to the origin database
- 3The database has no replication; add a replica and use synchronous commits so reads see the write
- 4Read replica replication lag; route reads-after-write to the primary or use a monotonic-read token
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.