Question 10
A database team reports a successful correction for this problem: A Spanner transactional system develops rising p99 read and write latency each month as the customer population grows. What evidence supports closing the incident?
Explanation
Correct Answer
Peak p99 latency returns within the agreed target without a new hot partition. The observed state validates the proposed fix: Use Spanner processing-unit and latency metrics to increase compute capacity and retest representative transactions. It addresses this cause: Provisioned compute capacity no longer matches the measured processing and storage workload.
Incorrect Answers
This finding relates to a situation in which an AlloyDB application suffers repeated buffer cache misses after a product catalog doubles in size. The current remediation must instead show that peak p99 latency returns within the agreed target without a new hot partition.
This finding relates to a situation in which a team chooses a cheap document database solely from per-GB storage price while its workload performs millions of reads daily. The current remediation must instead show that peak p99 latency returns within the agreed target without a new hot partition.
The result would be meaningful for a problem where an application proposes storing high-dimensional embeddings in a small PostgreSQL instance without sizing index memory. For this question, closure depends on confirming that peak p99 latency returns within the agreed target without a new hot partition.