Question 780
An earlier incident involved this issue: A service requires low-latency regional writes and no region-failure continuity, but deploys a costly multi-region Spanner configuration by default. Which continuing safeguard would address the risk?
Explanation
Correct Answer
Justify each multi-region placement with application and resilience requirements. It targets the actual operating weakness: The instance topology introduces cross-region quorum latency and cost without an approved requirement. The immediate repair was: Evaluate a compatible regional instance configuration against the actual availability and residency goals.
Incorrect Answers
This safeguard helps protect cases where a Bigtable deployment receives only one active node for a large sustained ingestion stream and queues requests under load. It leaves the main recurring failure untouched: the instance topology introduces cross-region quorum latency and cost without an approved requirement.
For the situation in which an AlloyDB deployment provisions very little storage planning capacity although the dataset grows by tens of gigabytes daily, it makes sense to include expected ingestion, retention and index growth in AlloyDB production acceptance. Here, the instance topology introduces cross-region quorum latency and cost without an approved requirement, so the safeguard misses the recurring fault.
The proposed check would document replication consistency expectations for client routing profiles, helping with cases where a Bigtable replicated workload routes consistency-sensitive read-after-write operations to a different cluster immediately after updates. The recurring exposure described here is that the instance topology introduces cross-region quorum latency and cost without an approved requirement.