Cloud SQL Proxy for secure connections in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of the Cloud SQL Proxy?

The Cloud SQL Proxy helps applications connect securely to Cloud SQL databases without managing IP allowlists or SSL certificates manually.

beginner

How does Cloud SQL Proxy authenticate connections to Cloud SQL?

It uses the credentials of the Google Cloud service account or user to authenticate securely with Cloud SQL instances.

intermediate

Which network protocol does Cloud SQL Proxy use to connect to Cloud SQL instances?

Cloud SQL Proxy uses secure TLS connections over TCP to connect to Cloud SQL instances.

intermediate

What is a key benefit of using Cloud SQL Proxy compared to direct IP connections?

It removes the need to open database ports to the public internet, reducing exposure and improving security.

advanced

Can Cloud SQL Proxy be used with multiple Cloud SQL instances simultaneously?

Yes, Cloud SQL Proxy can manage connections to multiple Cloud SQL instances at the same time using different instance connection names.

What does Cloud SQL Proxy eliminate the need for when connecting to Cloud SQL?

A Managing IP allowlists and SSL certificates

B Using service accounts

C Creating database users

D Writing SQL queries

Cloud SQL Proxy handles secure connections without requiring manual IP allowlists or SSL certificate management.

Which of the following is true about Cloud SQL Proxy authentication?

A It uses Google Cloud credentials for authentication

B It requires manual password entry every time

C It uses SSH keys for authentication

D It does not authenticate connections

Cloud SQL Proxy authenticates using Google Cloud service account or user credentials.

What type of connection does Cloud SQL Proxy establish to Cloud SQL instances?

A FTP

B Unencrypted HTTP

C TLS encrypted TCP

D UDP

Cloud SQL Proxy uses TLS encrypted TCP connections to secure data in transit.

Why is using Cloud SQL Proxy considered more secure than direct IP connections?

A It requires less bandwidth

B It avoids exposing database ports publicly

C It uses a faster protocol

D It stores passwords locally

Cloud SQL Proxy avoids opening database ports to the public internet, reducing attack surface.

Can Cloud SQL Proxy connect to multiple Cloud SQL instances at once?

A No, only one instance at a time

B Only if instances are in the same region

C Only with manual configuration per instance

D Yes, using different instance connection names

Cloud SQL Proxy supports simultaneous connections to multiple instances using their unique connection names.

Explain how Cloud SQL Proxy improves security when connecting to Cloud SQL databases.

Think about what risks are reduced by using the proxy.

Describe the authentication process Cloud SQL Proxy uses to connect to Cloud SQL instances.

Focus on how identity is verified automatically.

Practice

1. What is the main purpose of the Cloud SQL Proxy when connecting to a Cloud SQL database?

easy

A. To create a secure tunnel hiding credentials and IP addresses

B. To speed up database queries by caching results

C. To automatically backup the database

D. To convert SQL queries into NoSQL format

Solution

1. Step 1: Understand Cloud SQL Proxy role

   The Cloud SQL Proxy creates a secure connection tunnel to the Cloud SQL database, protecting credentials and IPs.

2. Step 2: Compare options

   Options A, B, and C describe unrelated functions like query conversion, caching, or backup, which are not proxy features.

3. Final Answer:

   To create a secure tunnel hiding credentials and IP addresses -> Option A

4. Quick Check:

   Cloud SQL Proxy = Secure tunnel [OK]

Hint: Proxy hides credentials and IPs for secure connection [OK]

Common Mistakes:

• Thinking proxy speeds up queries
• Confusing proxy with backup service
• Assuming proxy changes query types

2. Which command correctly starts the Cloud SQL Proxy for a Cloud SQL instance named my-instance in project my-project?

easy

A. gcloud sql proxy start --instance=my-instance

B. cloud_sql_proxy --instance=my-instance --project=my-project

C. cloud_sql_proxy -instances=my-project:us-central1:my-instance=tcp:5432

D. start_sql_proxy --project=my-project --instance=my-instance

Solution

1. Step 1: Recall correct Cloud SQL Proxy syntax

   The correct syntax uses -instances=project:region:instance=tcp:port format to specify the instance and port.

2. Step 2: Evaluate options

   cloud_sql_proxy -instances=my-project:us-central1:my-instance=tcp:5432 matches the correct syntax. Options A, C, and D use incorrect commands or flags not supported by Cloud SQL Proxy.

3. Final Answer:

   cloud_sql_proxy -instances=my-project:us-central1:my-instance=tcp:5432 -> Option C

4. Quick Check:

   Correct proxy start command = cloud_sql_proxy -instances=my-project:us-central1:my-instance=tcp:5432 [OK]

Hint: Use -instances=project:region:instance=tcp:port format [OK]

Common Mistakes:

• Using gcloud instead of cloud_sql_proxy command
• Wrong flag names like --instance instead of -instances
• Omitting region in instance name

3. 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?

medium

A. It connects securely to the Cloud SQL instance through the proxy

B. It connects to a local MySQL server running on port 3306

C. It fails because port 3306 is blocked by default

D. It connects directly to Cloud SQL without encryption

Solution

1. Step 1: Understand proxy port forwarding

   The proxy listens on localhost port 3306 and forwards connections securely to the Cloud SQL instance.

2. Step 2: Analyze connection behavior

   Connecting to localhost:3306 goes through the proxy tunnel, not a local database, ensuring secure access.

3. Final Answer:

   It connects securely to the Cloud SQL instance through the proxy -> Option A

4. Quick Check:

   Localhost port = proxy tunnel to Cloud SQL [OK]

Hint: 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

4. You started Cloud SQL Proxy with:
cloud_sql_proxy -instances=my-project:us-central1:my-instance=tcp:5432
Your app tries to connect to localhost:5432 but fails. What is the most likely cause?

medium

A. The proxy command is missing the database user flag

B. Port 5432 is already in use on localhost

C. The Cloud SQL instance is not in the us-central1 region

D. The app must connect to the Cloud SQL IP directly

Solution

1. Step 1: Check port conflict possibility

   If port 5432 is already used by another process, the proxy cannot bind to it, causing connection failure.

2. Step 2: Evaluate other options

   The Cloud SQL instance is not in the us-central1 region is unlikely if instance region is correct; The proxy command is missing the database user flag is incorrect because proxy does not require user flag; The app must connect to the Cloud SQL IP directly ignores proxy usage.

3. Final Answer:

   Port 5432 is already in use on localhost -> Option B

4. Quick Check:

   Port conflict = connection fail [OK]

Hint: Check if localhost port is free before starting proxy [OK]

Common Mistakes:

• Assuming proxy needs database user flag
• Trying to connect directly to Cloud SQL IP
• Ignoring port conflicts on localhost

5. You want to run Cloud SQL Proxy on a Compute Engine VM to allow multiple apps to connect securely to your Cloud SQL instance. Which approach is best to ensure secure and scalable connections?

hard

A. Connect apps directly to Cloud SQL IP with SSL certificates, skipping the proxy

B. Run separate Cloud SQL Proxy instances per app on different ports on the VM

C. Use Cloud SQL Proxy only locally on developer machines, not on VMs

D. Run one Cloud SQL Proxy instance on the VM, listening on a shared port, and configure apps to connect to localhost

Solution

1. Step 1: Understand proxy usage on shared VM

   Running a single proxy instance on the VM listening on one port allows multiple apps to connect securely via localhost, simplifying management.

2. Step 2: Evaluate alternatives

   Run separate Cloud SQL Proxy instances per app on different ports on the VM adds complexity with multiple proxies; Connect apps directly to Cloud SQL IP with SSL certificates, skipping the proxy exposes IP and requires SSL setup; Use Cloud SQL Proxy only locally on developer machines, not on VMs limits proxy use unnecessarily.

3. Final Answer:

   Run one Cloud SQL Proxy instance on the VM, listening on a shared port, and configure apps to connect to localhost -> Option D

4. Quick Check:

   Single proxy instance for multiple apps = best practice [OK]

Hint: One proxy instance per VM, multiple apps connect locally [OK]

Common Mistakes:

• Running multiple proxies causing port conflicts
• Skipping proxy and exposing IPs
• Limiting proxy use to local machines only