Question 70
A database team wants evidence that it fixed this issue: A product search API reads from the primary even as catalog traffic grows and writes remain light. Which result would verify success?
Explanation
Correct Answer
Peak search latency improves and the primary retains headroom for writes. The observed state validates the proposed fix: Evaluate read replicas and move eligible reads off the primary with explicit freshness controls. It addresses this cause: Read-only queries share limited primary capacity although the application can tolerate bounded staleness.
Incorrect Answers
This finding belongs with a situation in which a ticketing service running on Cloud SQL for PostgreSQL rejects new sessions during a marketing event while CPU remains moderate. The required acceptance finding here is that peak search latency improves and the primary retains headroom for writes.
This finding belongs with a situation in which a Spanner transactional system develops rising p99 read and write latency each month as the customer population grows. The required acceptance finding here is that peak search latency improves and the primary retains headroom for writes.
The result would be meaningful for a problem where an audit investigation cannot identify who modified a database instance because only application query logs were collected. For this question, closure depends on confirming that peak search latency improves and the primary retains headroom for writes.