Read replicas are added to a database to handle a growing volume of read traffic. After deployment, the application occasionally returns an outdated result to a user who has just made a change. The most likely cause is:

Question

Accepted Answer

The user's read landed on a replica that had not yet received the most recent change from the primary because of replication lag.

Answer

The cache layer has been incorrectly configured and is serving expired data to the application instead of fetching fresh values.

Answer

The replicas have lost their connection to the primary and are serving data from the last successful synchronization point in time.

Answer

The application is sending writes to the replicas, which silently discard them rather than forwarding the writes to the primary.

Crowdly

Read replicas are added to a database to handle a growing volume of read traffic...

Want instant access to all verified answers on moodle.polytechnic.bh?