You are planning connectivity for a global retail analytics service that runs in multiple Google Cloud regions and must reach a Cloud Spanner database with very low latency, strong security, and…

Question

Options

• AUse the Cloud Spanner client libraries with a regional instance and enable connection pooling
• BUse the Cloud Spanner client libraries against a multi-region instance and configure connection
• CAccess Cloud Spanner through the REST API from the app and add a cache layer to improve
• DConnect to a fixed public IP address on the Cloud Spanner instance and enable SSL

• A
  6% (3)
• B
  79% (41)
• C
  2% (1)
• D
  13% (7)

Explanation

The Cloud Spanner client libraries are purpose-built for Spanner: they automatically route requests to the nearest replica (minimizing latency), manage session pools, handle retries with exponential backoff, and use encrypted gRPC channels (strong security). Pairing them with a multi-region instance ensures replicas exist close to each application region, satisfying low latency globally and high reliability. Option A limits the topology to a single region. Option C adds a cache layer that breaks strong consistency and increases complexity. Option D is invalid-Cloud Spanner does not expose a fixed public IP; connectivity is always through Google's network and the client libraries.

No community discussion yet for this question.