Question 180
An earlier incident involved this issue: A team adds broad external network access to troubleshoot a private Cloud SQL deployment and exposes the service beyond the intended boundary. Which continuing safeguard would address the risk?
Explanation
Correct Answer
Review network exposure after temporary database connectivity exceptions. The original failure arose from: The connectivity workaround bypasses the approved private-only access model. The control reduces that failure mode.
Incorrect Answers
For the situation in which a production team embeds a database password in a container image so rotating the credential requires an application rebuild, it makes sense to scan application artifacts and use governed credential rotation. Here, the connectivity workaround bypasses the approved private-only access model, so the safeguard misses the recurring fault.
The failure in the question arises because the connectivity workaround bypasses the approved private-only access model. A safeguard to test TLS certificate rollover with representative clients before expiration serves situations where a PostgreSQL client begins rejecting encrypted database sessions after a server certificate rollover rather than this one.
This would map backup frequency, log retention, and PITR capability to each application's RPO. It is useful when a Cloud SQL service promises recovery to within five minutes, but backups are only taken nightly, but it does not prevent the issue here: the connectivity workaround bypasses the approved private-only access model.