Exam Professional Cloud Developer topic 1 question 10 discussion

The more number of node less read latency hence i will go with option A and C

I think the answer should be A) + something. They wants 99.999% availability - only multi-regional instance fits this. To minimize read latency nam-asia-eur1 instance works best as it has replicas in Noth America, Europe and Asia regions. As for second answer - I do not have strong opinion.. As per documentation "Adding nodes gives each replica more CPU and RAM, which increases the replica's throughput" and they recommend to choose number of nodes to "keep high priority total CPU utilization under 65%". So nodes are not about SLA and read latency. From another hand spanner "Cloud Spanner automatically replicates your data between regions with strong consistency guarantees" so no DataFlow pipeline needed to replicate data, unless the app has other DBs and ETL between Spanner and that DBs.

To achieve 99.999% availability and minimize read latency for a globally distributed user base, the company should: - Deploy a multi-regional Cloud Spanner instance with the "nam-asia-eur1" configuration (Option A). This setup will provide the geographical distribution of data across three continents — North America, Asia, and Europe. The multi-regional nature of this option is designed to maintain high availability and ensure users across these regions experience low latency when accessing the database. - Ensure that the Cloud Spanner instance has a minimum of three nodes (Option C). This configuration will contribute to the high availability and fault tolerance of the database. Spanner's built-in replication across these nodes in different regions will further support the five nines (99.999%) availability target, while also providing scalability for read operations.

Let's think about all possible answers: - B does not make sense, as "nam3" is not the global configuration we want; - D is not ok, 'cause 1 node is not enough - E is not enough, as we want a global configuration; - F is totally unrelated.

AC are best suited here.

99.999% availability and reduce latency Option A gives us 99.999% availability (think its typo in region name) Option C is about compute capacity, more nodes -> less latency https://cloud.google.com/spanner/docs/instances#compute-capacity B - there is no such multi-region configuration nam3 D - its better to create cluster with 3 nodes, not 1 E,F - overengineering

A - global and provides 99.999% availability C - more nodes - less latency

it's obvious

why not C and F

3 regions at least, and for those that says there is no region "man-asia-eur1", take a look at the console, its multiregion nomenclature!

There is no region called ""nam-asia-eur1"" A is wrong, B&C is correct

We need multi-regin db (spanner) to satisfy 99,999% SLA and have multi-node to ensure resource needed.

AC are correct

C because the number of nodes increases the computational capabilities ( queries for seconds and so minor latency), F to cover worldwide availability; A it's wrong because the configuration "nam-asia-eur1" not exist, Google suggests "nam-eur-asia1" o "nam-eur-asia3", D it's wrong because the number of nodes is too few; E is too expensive a solution

A and C make sense

This should be A and F.

Agree with A and C