How should you implement high availability for your Bigtable deployment when expanding to the APAC region, following Google's recommended practices, after launching a new product in the US market with two existing clusters in a single US region?

Exam-Like

Maintain a target of 23% CPU utilization by locating: cluster-a in zone us-central1-a cluster-b in zone europe-west1-d cluster-c in zone asia-east1-b

0.0%

Maintain a target of 23% CPU utilization by locating: cluster-a in zone us-central1-a cluster-b in zone us-central1-b cluster-c in zone us-east1-a

9.5%

Maintain a target of 35% CPU utilization by locating: cluster-a in zone us-central1-a cluster-b in zone australia-southeast1-a cluster-c in zone europe-west1-d cluster-d in zone asia-east1-b

14.3%

Maintain a target of 35% CPU utilization by locating: cluster-a in zone us-central1-a cluster-b in zone us-central2-a cluster-c in zone asia-northeast1-b cluster-d in zone asia-east1-b

76.2%

Google Professional Cloud Database Engineer

Get started today

Comments

How should you implement high availability for your Bigtable deployment when expanding to the APAC region, following Google's recommended practices, after launching a new product in the US market with two existing clusters in a single US region?