You recently joined a new team that has a Cloud Spanner database instance running in production. Your manager has asked you to optimize the Spanner instance to reduce cost while maintaining high relia

Question

Options

• AUse Cloud Logging to check for error logs, and reduce Spanner processing units by small
• BUse Cloud Trace to monitor the requests per sec of incoming requests to Spanner, and reduce
• CUse Cloud Monitoring to monitor the CPU utilization, and reduce Spanner processing units by
• DUse Snapshot Debugger to check for application errors, and reduce Spanner processing units by

• A
  8% (2)
• B
  16% (4)
• C
  72% (18)
• D
  4% (1)

Explanation

Cloud Spanner's primary sizing metric is CPU utilization. Cloud Monitoring exposes spanner.googleapis.com/instance/cpu/utilization metrics that directly indicate whether the instance is over-provisioned. The best practice is to reduce processing units in small increments while watching CPU stay well below the recommended threshold (~65% for single-region, ~45% for multi-region), ensuring reliability is never compromised. Cloud Logging error logs (A) indicate application problems, not spare capacity. Cloud Trace (B) measures request latency and throughput but is not the right signal for capacity decisions. Snapshot Debugger (D) is a code-level debugging tool with no relevance to instance sizing.

No community discussion yet for this question.