PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #115
You are troubleshooting a connection issue with a newly deployed Cloud SQL instance on Google Cloud. While investigating the Cloud SQL Proxy logs, you see the message Error 403: Access Not Configured.
The correct answer is C. Enable the Cloud SQL Admin API.. The correct answer is C. The error message 'Error 403: Access Not Configured' from the Cloud SQL Proxy specifically indicates that the Cloud SQL Admin API has not been enabled in the Google Cloud project. The Cloud SQL Proxy requires this API to be active to authenticate and esta
Question
You are troubleshooting a connection issue with a newly deployed Cloud SQL instance on Google Cloud. While investigating the Cloud SQL Proxy logs, you see the message Error 403:
Access Not Configured. What should you do?
Options
- ACheck the app.yaml value cloud_sql_instances for a misspelled or incorrect instance connection
- BCheck whether your service account has cloudsql.instances.connect permission.
- CEnable the Cloud SQL Admin API.
- DEnsure that you are using an external (public) IP address interface.
How the community answered
(24 responses)- B4% (1)
- C92% (22)
- D4% (1)
Explanation
The correct answer is C. The error message 'Error 403: Access Not Configured' from the Cloud SQL Proxy specifically indicates that the Cloud SQL Admin API has not been enabled in the Google Cloud project. The Cloud SQL Proxy requires this API to be active to authenticate and establish connections. Enabling it via the Google Cloud Console or gcloud resolves this error immediately. Option A (misspelled instance connection name) would typically produce a 'not found' or connection-refused type error, not a 403. Option B (missing IAM permission) would produce a 'permission denied' message rather than 'Access Not Configured.' Option D (external IP) is unrelated to this specific error message.
Topics
Community Discussion
No community discussion yet for this question.