Question 810
The following database problem was corrected: A Spanner schema change introduces a new index and large backfill work without checking user-facing transaction latency. Which result demonstrates that the root cause was addressed?
Explanation
Correct Answer
The index becomes usable while key production queries remain within SLA. This distinguishes actual recovery from a merely healthy-looking console. The targeted correction was: Stage the index change and monitor supported schema operation status and transaction performance.
Incorrect Answers
Even if this observation were recorded, it would support a case where a multinational application needs continued transactional availability after one region fails but its Spanner database was deployed regionally. It would not verify that the index becomes usable while key production queries remain within SLA.
The result would be meaningful for a problem where a service requires low-latency regional writes and no region-failure continuity, but deploys a costly multi-region Spanner configuration by default. For this question, closure depends on confirming that the index becomes usable while key production queries remain within SLA.
Even if this observation were recorded, it would support a case where an API needs to scale a high volume of eventually consistent catalog reads but all requests target the single Cloud SQL writer. It would not verify that the index becomes usable while key production queries remain within SLA.