Databases · Senior · Question 17 of 75
A user updates their profile and immediately sees the old data. Reads go to replicas. What's the issue and fix?
- ✓Correct answer: Replication lag breaks read-your-writes; route that user's reads to the primary for a short time or until the replica reaches the write's LSN
- 2The cache must be disabled entirely
- 3The primary lost the write
Explanation
Options include sticky primary reads after writes, waiting for the replica to replay a given WAL position, or reading critical data only from the primary.