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

Question

Options

• AUse the default app profile with single-cluster routing.
• BUse the default app profile with multi-cluster routing.
• CCreate a custom app profile with multi-cluster routing.
• DCreate a custom app profile with single-cluster routing.

• A
  3% (1)
• B
  6% (2)
• C
  75% (24)
• D
  16% (5)

Explanation

Options A and D use single-cluster routing, which directs all requests to one specific cluster. If that cluster becomes unavailable, there is no automatic failover - these options do not meet the requirements. Option B uses the default app profile with multi-cluster routing. Multi-cluster routing does enable automatic failover, but using the default app profile is not recommended for production workloads because it may not be configured with the appropriate settings for your specific application, and it is shared among all applications that don't specify a profile. Option C is correct: creating a custom app profile with multi-cluster routing gives you automatic failover (requests are transparently routed to the available cluster if one goes down) while also allowing you to configure profile settings specifically for this banking application. For production workloads, Google recommends using custom app profiles to isolate routing policies and configurations per application.

No community discussion yet for this question.