Google Cloud Certified Professional Cloud Database Engineer Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose D1

  Problem: High read latency after new version launch. You want actionable insight to fix the latency. READ_STATS (Option C) only tells tables being read and total latency—not the specific queries. QUERY_STATS (Option D) tells which queries are slow, so you can optimize them → directly addressing the issue. Conclusion: C is useful for general read metrics, but D is the correct choice to troubleshoot and improve performance. In short: READ_STATS = tables, QUERY_STATS = queries → your problem is query latency → use QUERY_STATS.

• Chose C2

  SPANNER_SYS.READ_STATS* contains statistics about reads.

• Chose D1

  When experiencing high read latency in a Cloud Spanner instance, analyzing the SPANNER_SYS.QUERY_STATS tables provides valuable insights into the performance of your queries. These tables contain statistics about query execution, such as latency, execution count, and resource usage. This information helps identify slow or inefficient queries that may be causing the performance degradation