Bird
0
0

Why might a read replica in Cloud SQL lag behind the primary instance, and what is the impact?

hard📝 Conceptual Q10 of 15
GCP - Cloud SQL and Databases

Why might a read replica in Cloud SQL lag behind the primary instance, and what is the impact?

ABecause primary is offline; impact is data loss on replica
BBecause replica is overloaded; impact is write failures on primary
CBecause replication is asynchronous; impact is stale reads on replica
DBecause replica uses a different database engine; impact is query errors
Step-by-Step Solution
Solution:

  1. Step 1: Understand asynchronous replication effect

    Asynchronous replication causes delay, so replica may not have latest data immediately.

  2. Step 2: Identify impact on reads

    Reads from replica may be stale, but primary remains consistent.

  3. Final Answer:

    Because replication is asynchronous; impact is stale reads on replica -> Option C

  4. Quick Check:

    Lag cause and impact = Async replication, stale reads [OK]
Quick Trick: Async replication causes lag and stale reads [OK]
Common Mistakes:
  • Confusing lag with write failures
  • Assuming primary offline causes lag
  • Mixing database engine differences with replication lag

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More GCP Quizzes
Cloud Firestore and Bigtable - Memorystore for Redis caching - Quiz 14medium Cloud Firestore and Bigtable - Real-time updates with listeners - Quiz 1easy Cloud Firestore and Bigtable - Real-time updates with listeners - Quiz 14medium Cloud Functions - Environment variables and secrets - Quiz 12easy Cloud IAM Advanced - IAM deny policies - Quiz 13medium Cloud Pub/Sub - Message ordering - Quiz 4medium Cloud Pub/Sub - Message retention and acknowledgment - Quiz 13medium Cloud SQL and Databases - Creating a Cloud SQL instance - Quiz 2easy Cloud SQL and Databases - Backup and restore - Quiz 11easy Cloud SQL and Databases - Creating a Cloud SQL instance - Quiz 8hard