Question 740
A database team wants to prevent a recurrence of this issue: An AlloyDB deployment provisions very little storage planning capacity although the dataset grows by tens of gigabytes daily. Which preventive practice is most relevant?
Explanation
Correct Answer
Include expected ingestion, retention and index growth in AlloyDB production acceptance. The original failure arose from: Operational growth and applicable service limits were not incorporated into the instance rollout. The control reduces that failure mode.
Incorrect Answers
The failure in the question arises because operational growth and applicable service limits were not incorporated into the instance rollout. A safeguard to include service-owner signoff of maintenance settings at provisioning serves situations where a Cloud SQL administrator leaves maintenance settings uncontrolled during rollout of a service with defined weekly blackout windows rather than this one.
The failure in the question arises because operational growth and applicable service limits were not incorporated into the instance rollout. A safeguard to schedule failover validation after infrastructure or database driver changes serves situations where a database service looks healthy after deployment yet its automatic failover path has never been exercised with the application rather than this one.
The proposed check would require representative database operations as an infrastructure readiness gate, helping with cases where a new AlloyDB deployment reports healthy virtual resources while its application user cannot commit a simple transaction. The recurring exposure described here is that operational growth and applicable service limits were not incorporated into the instance rollout.