Your team currently uses Bigtable as their database backend. In your application's app profile, you notice that the connection to the Bigtable cluster is specified as single-cluster routing, and the c

Question

Options

• ASet up Memcached so that queries hit the cache layer first and automatically get data from
• BIncrease the Bigtable client's connection pool size.
• CConfigure a Dataflow template, and use a Beam connector to stream data changes.
• DConfigure the app profile to use multi-cluster routing.

• A
  3% (1)
• B
  7% (2)
• C
  13% (4)
• D
  77% (23)

Explanation

Bigtable's multi-cluster routing automatically routes each request to the nearest available cluster and handles failover transparently without manual intervention. Single-cluster routing with manual failover means that if the primary cluster becomes unavailable, a human must intervene-this is neither efficient nor highly available. Switching the app profile to multi-cluster routing requires only a configuration change (no code changes), immediately delivering both lower latency (routing to the closest cluster) and automatic high availability. Options A (Memcached) and C (Dataflow) address different problems entirely, and increasing the connection pool (B) improves throughput but does nothing for availability.

No community discussion yet for this question.