Topic 1 Question 10
2 つ選択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?
Create a multi-regional Cloud Spanner instance with "nam-asia-eur1" configuration.
Create a multi-regional Cloud Spanner instance with "nam3" configuration.
Create a cluster with at least 3 Spanner nodes.
Create a cluster with at least 1 Spanner node.
Create a minimum of two Cloud Spanner instances in separate regions with at least one node.
Create a Cloud Dataflow pipeline to replicate data across different databases.
ユーザの投票
コメント(17)
The more number of node less read latency hence i will go with option A and C
👍 8saurabh18052020/11/06I 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. (https://cloud.google.com/spanner/docs/instances#configs-multi-region)
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.
👍 7emmet2020/05/27https://cloud.google.com/spanner/docs/instances
Above link supports A for "users across the globe" as per qn
https://cloud.google.com/spanner/docs/latency
Above link supports C for "minimize the read latency "
👍 6syu31svc2021/06/19
シャッフルモード