Question 760
A postincident review documents: A Cloud SQL administrator leaves maintenance settings uncontrolled during rollout of a service with defined weekly blackout windows. Which ongoing check targets the underlying failure?
Explanation
Correct Answer
Include service-owner signoff of maintenance settings at provisioning. The recurring risk is maintenance options were not reconciled with the application's approved availability schedule. This check makes that risk visible before another incident.
Incorrect Answers
This would check network attachment and public IP exposure after every database creation. It is useful when Cloud SQL for MySQL is configured with public addressing while the application design specifies database access only through a private VPC, but it does not prevent the issue here: maintenance options were not reconciled with the application's approved availability schedule.
The proposed check would include column-family retention rules in initial Bigtable table creation, helping with cases where a Bigtable team retains every version of rapidly changing cell values even though policy requires only the latest two versions. The recurring exposure described here is that maintenance options were not reconciled with the application's approved availability schedule.
This control would verify endpoint routing and query consistency after creating read replicas or pools; it responds to the risk in which an application launches an AlloyDB read pool but leaves every reporting connection pointed at the primary endpoint. It would not address the current root cause: maintenance options were not reconciled with the application's approved availability schedule.