Question 300
An earlier incident involved this issue: A developer can query Spanner using a personal account but the production workload cannot read the same table. Which continuing safeguard would address the risk?
Explanation
Correct Answer
Include service-identity access tests before promotion from development. This is preventive rather than a one-time repair; it addresses the underlying failure: Production access was not granted to the service identity actually making the API call.
Incorrect Answers
This control would test Google Cloud IAM and database SQL privileges as distinct authorization layers; it responds to the risk in which a new Cloud SQL administrator cannot inspect an instance in the console even though their PostgreSQL database user has superuser permissions. It would not address the current root cause: production access was not granted to the service identity actually making the API call.
This would review encryption key rotation and destruction against backup retention obligations. It is useful when a database backup is encrypted with a customer-managed key that the team plans to destroy before retention expires, but it does not prevent the issue here: production access was not granted to the service identity actually making the API call.
This control would review schema permissions when new tables, views, or database roles are introduced; it responds to the risk in which an application reaches Cloud SQL but receives permission denied for one schema after a team reorganizes SQL roles. It would not address the current root cause: production access was not granted to the service identity actually making the API call.