[Solved] Given this command to start Cloud SQL Proxy:cloud_sql_proxy -instances=my-project:us-central1:my-instance=tcp:3306What happens when your application connects to localhost:3306? | GCP

GCP - Cloud SQL and Databases

Given this command to start Cloud SQL Proxy:
cloud_sql_proxy -instances=my-project:us-central1:my-instance=tcp:3306
What happens when your application connects to localhost:3306?

AIt connects securely to the Cloud SQL instance through the proxy

BIt connects to a local MySQL server running on port 3306

CIt fails because port 3306 is blocked by default

DIt connects directly to Cloud SQL without encryption

Step-by-Step Solution

Solution:

Step 1: Understand proxy port forwarding
The proxy listens on localhost port 3306 and forwards connections securely to the Cloud SQL instance.
Step 2: Analyze connection behavior
Connecting to localhost:3306 goes through the proxy tunnel, not a local database, ensuring secure access.
Final Answer:
It connects securely to the Cloud SQL instance through the proxy -> Option A
Quick Check:
Localhost port = proxy tunnel to Cloud SQL [OK]

Quick Trick: Localhost port forwards securely via proxy to Cloud SQL [OK]

Common Mistakes:

Assuming connection is to local database
Thinking port 3306 is blocked by default
Believing connection skips encryption

Master "Cloud SQL and Databases" in GCP

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More GCP Quizzes

Given this command to start Cloud SQL Proxy:

Step 1: Understand proxy port forwarding

Step 2: Analyze connection behavior

Final Answer:

Quick Check:

Want More Practice?