Exam Professional Cloud Database Engineer topic 1 question 4 discussion

Read statistics provide insight into how an application is using the database, and are useful when investigating performance issues. https://cloud.google.com/spanner/docs/introspection/read-statistics

SPANNER_SYS.READ_STATS* contains statistics about reads.

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

SPANNER_SYS.QUERY_STATS tables: the first step in diagnosing latency after a code change is often to look at the queries themselves so ans is D https://cloud.google.com/spanner/docs/introspection/query-statistics

C! You should analyze the situation before changing the architecture so drastically.

C is the correct answer

C is definitely the correct answer here. SPANNER_SYS.READ_STATS* contains statistics about reads.

C is the correct answer

C. Read stats

C. A Query parameters is vague at best. B would not achieve anything. C and D look interesting, but as others have stated, querying the READ_STATS* tables would give you information about what is causing read issues. So C is the best answer.

C. Use SQL statements to analyze SPANNER_SYS.READ_STATS* tables

C. Use SQL statements to analyze SPANNER_SYS.READ_STATS* tables

C. Use SQL statements to analyze SPANNER_SYS.READ_STATS* tables. To troubleshoot high read latency, you can use SQL statements to analyze the SPANNER_SYS.READ_STATS* tables. These tables contain statistics about read operations in Cloud Spanner, including the number of reads, read latency, and the number of read errors. By analyzing these tables, you can identify the cause of the high read latency and take appropriate action to resolve the issue. Other options, such as using query parameters to speed up frequently executed queries or changing the Cloud Spanner configuration from multi-region to single region, may not be directly related to the issue of high read latency. Similarly, analyzing the SPANNER_SYS.QUERY_STATS* tables, which contain statistics about query operations, may not be relevant to the issue of high read latency.

C: Use SQL statements to analyze ***** SPANNER_SYS.READ_STATS* tables.

C is the correct answer

B - Is correct

Read statistics provide insight into how an application is using the database, and are useful when investigating performance issues . https://cloud.google.com/spanner/docs/introspection/read-statistics#when_to_use_read_statistics