Question

Difficulty: MediumManaging Storage and Database Solutions

Your team manages a high-throughput sensor application that stores real-time metrics in a Cloud Bigtable instance. During peak operational hours, read and write latencies spike significantly because average node CPU utilization exceeds 90%. You need to resolve this performance bottleneck during peak traffic while ensuring cost-efficient operations and minimal administrative overhead. Which two actions should you take? (Select TWO answers.)

  1. Enable autoscaling on the Cloud Bigtable cluster and configure a target CPU utilization threshold.Answer
  2. Manually increase the node count of the Cloud Bigtable cluster prior to predicted peak traffic windows.Answer
  3. C
    Migrate the real-time time-series workload to a Cloud SQL PostgreSQL database instance with storage auto-increase enabled.
  4. D
    Reconfigure the Cloud Bigtable cluster storage type from SSD to HDD to decrease storage access latency.

Answer

The correct actions are to enable Cloud Bigtable autoscaling with a target CPU threshold and to manually increase the cluster node count to handle peak traffic.
Cloud Bigtable scales performance linearly by adjusting the number of nodes in a cluster. Adding nodes increases compute capacity and reduces CPU load per node, directly resolving latency spikes. Configuring Cloud Bigtable autoscaling automates node management based on CPU utilization targets, while manually scaling nodes allows proactive capacity adjustments.

Step-by-Step Solution

1
Identify the cause of performance degradation
High read/write latencies occur due to CPU utilization exceeding 90% across Bigtable nodes.
Cloud Bigtable compute capacity and overall throughput scale linearly with the number of nodes in a cluster.
2
Evaluate scale-out solutions for Bigtable
Adding nodes manually or enabling autoscaling based on CPU targets increases compute resources per cluster.
Both manual node adjustments and autoscaling dynamically allocate nodes to lower CPU load without requiring downtime or schema migration.

Key Concept

Managing Cloud Bigtable performance and node scaling
Rate this question