Topic 1 Question 109
You have an application that sends banking events to Bigtable cluster-a in us-east. You decide to add cluster-b in us-central1. Cluster-a replicates data to cluster-b. You need 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. What deployment strategy should you use?
Use the default app profile with single-cluster routing.
Use the default app profile with multi-cluster routing.
Create a custom app profile with multi-cluster routing.
Create a custom app profile with single-cluster routing.
ユーザの投票
コメント(9)
C - Even the default profile can be single-cluster or multi-cluster "The settings in an instance's default app profile depend on the number of clusters the instance had when you first created it:
If you created the instance with 1 cluster, the default app profile uses single-cluster routing, and it enables single-row transactions. This ensures that adding additional clusters later doesn't change the behavior of your existing applications."
👍 5marpayer2023/01/10- 正解だと思う選択肢: B
Default profile can be single-cluster or multi-cluster https://cloud.google.com/bigtable/docs/app-profiles#:~:text=Multi%2Dcluster%20routing%20automatically%20routes,they%20are%20in%20different%20zones.
👍 2chelbsik2022/12/26 A The default app profile does not change when you add or remove clusters. You must manually update the default app profile to change its settings. However, as a best practice you should create and use a new app profile instead of changing the default app profile.
👍 2SandyZA2022/12/28
シャッフルモード