Question 200
The previous outage involved this problem: A Cloud SQL public-IP deployment permits connections from a wide internet CIDR merely to support one fixed corporate egress. What long-term control addresses the risk?
Explanation
Correct Answer
Audit database ingress allowlists for oversized address ranges. The recurring risk is authorized networks were configured much more broadly than the required client source. This check makes that risk visible before another incident.
Incorrect Answers
This would test private database reachability for each application runtime type. It is useful when a private database can be contacted from a VM but the same request fails from a serverless runtime in another network, but it does not prevent the issue here: authorized networks were configured much more broadly than the required client source.
For the situation in which a mobile app needs synchronized document-oriented user profiles with flexible fields and client SDK integration, it makes sense to validate document size, query patterns, and security rules before choosing a store. Here, authorized networks were configured much more broadly than the required client source, so the safeguard misses the recurring fault.
This control would test TLS certificate rollover with representative clients before expiration; it responds to the risk in which a PostgreSQL client begins rejecting encrypted database sessions after a server certificate rollover. It would not address the current root cause: authorized networks were configured much more broadly than the required client source.