Bird
0
0

You configured a Cloud Spanner instance with instance_config = "nam3" but your app experiences high latency in Europe. What is the likely cause?

medium📝 Debug Q14 of 15
GCP - Cloud SQL and Databases
You configured a Cloud Spanner instance with instance_config = "nam3" but your app experiences high latency in Europe. What is the likely cause?
AThe instance_config "nam3" is invalid and causes errors.
BYou need to increase the number of nodes to reduce latency.
CThe multi-region config "nam3" only covers North America, not Europe.
DCloud Spanner does not support multi-region configurations.
Step-by-Step Solution
Solution:
  1. Step 1: Understand "nam3" coverage

    "nam3" is a multi-region config limited to North America regions only.
  2. Step 2: Analyze latency cause

    High latency in Europe happens because data is not stored close to European users.
  3. Final Answer:

    The multi-region config "nam3" only covers North America, not Europe. -> Option C
  4. Quick Check:

    nam3 excludes Europe, causing latency there [OK]
Quick Trick: Check if multi-region config covers your app's user locations [OK]
Common Mistakes:
  • Assuming multi-region covers all continents
  • Thinking node count fixes geographic latency
  • Believing "nam3" is invalid

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More GCP Quizzes