Bird
0
0

After creating a read replica, you notice it is not marked as read-only. What should you do to fix this?

medium📝 Debug Q7 of 15
GCP - Cloud SQL and Databases

After creating a read replica, you notice it is not marked as read-only. What should you do to fix this?

ARestart the primary instance
BUpdate the replica to the latest database engine version
CDelete and recreate the replica with correct flags
DEnable the read-only flag on the replica instance settings
Step-by-Step Solution
Solution:

  1. Step 1: Identify how to enforce read-only mode

    Replica instances have a read-only flag that must be enabled to prevent writes.

  2. Step 2: Choose corrective action

    Enabling the flag fixes the issue without recreating or restarting other instances.

  3. Final Answer:

    Enable the read-only flag on the replica instance settings -> Option D

  4. Quick Check:

    Read-only mode = Enable flag [OK]
Quick Trick: Set read-only flag to true on replicas [OK]
Common Mistakes:
  • Restarting unrelated instances
  • Recreating replica unnecessarily
  • Ignoring read-only flag settings

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