Google Professional Cloud Database Engineer
Get started today
Ultimate access to all questions.
What deployment strategy should you implement to ensure Bigtable maintains read and write availability by automatically routing requests to the alternate cluster if either cluster-a in us-east or cluster-b in us-central1 becomes unavailable, given that data replicates from cluster-a to cluster-b?
What deployment strategy should you implement to ensure Bigtable maintains read and write availability by automatically routing requests to the alternate cluster if either cluster-a in us-east or cluster-b in us-central1 becomes unavailable, given that data replicates from cluster-a to cluster-b?
Explanation:
To ensure that Bigtable continues to accept read and write requests if one of the clusters becomes unavailable and that requests are routed automatically to the other cluster, you should use a custom app profile with multi-cluster routing. The default app profile does not support multi-cluster routing, which is necessary for automatic failover between clusters. Single-cluster routing does not provide the required failover capability. Therefore, creating a custom app profile with multi-cluster routing is the correct strategy to meet the requirements.