Bird
0
0

If a read replica lags behind the primary database, what is the likely impact on application read queries directed to the replica?

medium📝 service behavior Q5 of 15
AWS - RDS and Relational Databases
If a read replica lags behind the primary database, what is the likely impact on application read queries directed to the replica?
AApplication may read stale data from the replica
BApplication will receive write errors
CReplica will reject all read queries
DReplica automatically updates instantly with no lag
Step-by-Step Solution
Solution:
  1. Step 1: Understand replication lag

    Replication lag means the replica is behind the primary in data updates.
  2. Step 2: Effect on reads

    Reads from the replica may return outdated (stale) data until lag catches up.
  3. Final Answer:

    Application may read stale data from the replica -> Option A
  4. Quick Check:

    Replication lag causes stale reads = A [OK]
Quick Trick: Lag causes stale reads, not errors or rejections [OK]
Common Mistakes:
MISTAKES
  • Assuming lag causes write errors
  • Thinking replica rejects reads during lag

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes