GOOGLE-PROFESSIONAL-CLOUD-DEVELOPER practice question 16 of 35

Your company wants to expand their users outside the United States for their popular application. The company wants to ensure 99.999% availability of the database for their application and also wants to minimize the read latency for their users across the globe. Which two actions should they take? (Choose two.)

Full set: 265 questions
Answer options
A: Create a multi-regional Cloud Spanner instance with "nam-asia-eur1" configuration. Correct answer
B: Create a multi-regional Cloud Spanner instance with "nam3" configuration.
C: Create a cluster with at least 3 Spanner nodes. Correct answer
D: Create a cluster with at least 1 Spanner node.
E: Create a minimum of two Cloud Spanner instances in separate regions with at least one node.
F: Create a Cloud Dataflow pipeline to replicate data across different databases.
Correct Answer:
A. Create a multi-regional Cloud Spanner instance with "nam-asia-eur1" configuration.; C. Create a cluster with at least 3 Spanner nodes.
Explanation

To achieve 99.999% availability and low-latency global reads, a multi-regional Cloud Spanner instance is the appropriate solution. The 99.999% availability SLA is specifically offered for multi-region configurations. The nam-asia-eur1 configuration places read-write and read-only replicas across North America, Europe, and Asia. This geographic distribution is essential for minimizing read latency for a global user base. Furthermore, creating any multi-region Cloud Spanner instance has a mandatory minimum requirement of 3 nodes to support the underlying replicas and maintain quorum for writes. Therefore, selecting a multi-region configuration and provisioning at least 3 nodes are the necessary actions.

Why Incorrect

B. The "nam3" configuration places all replicas within North America, which would not minimize read latency for users in other parts of the world.
D. A multi-regional Cloud Spanner instance requires a minimum of 3 nodes to be created, not 1. One node is the minimum for a regional instance.
E. Managing two separate instances requires manual data replication, adds complexity, and does not guarantee the strong consistency that a single multi-region instance provides.
F. Using Cloud Dataflow for replication is an asynchronous, complex solution for a problem that Cloud Spanner's synchronous, built-in replication solves natively and with strong consistency.

References

1. Google Cloud Documentation - Cloud Spanner Instances: "Multi-region configurations distribute the database's replicas in multiple regions... This configuration enables you to get lower read latency from multiple locations across the globe... For example, in the nam-asia-eur1 configuration, Spanner maintains replicas in us-central1, europe-west1, and asia-east1." This supports option A.

2. Google Cloud Documentation - Cloud Spanner Instances (Compute Capacity section): "When you create an instance, you must specify the number of nodes or processing units... Regional instances must have at least 1 node (1000 processing units). Multi-region instances must have at least 3 nodes (3000 processing units)." This supports option C as a requirement for option A.

3. Google Cloud Documentation - Cloud Spanner Service Level Agreement (SLA): "For each Cloud Spanner instance with a Multi-Region instance configuration, Google will use commercially reasonable efforts to make the instance available with a Monthly Uptime Percentage of at least 99.999%." This confirms the availability requirement is met by a multi-region configuration.

Scroll to Top