Cloud SQL Proxy for secure connections in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start the Cloud SQL Proxy with the correct instance connection name.

GCP

cloud_sql_proxy -instances=[1]=tcp:5432

Drag options to blanks, or click blank then click option'

Amy-project:us-central1:my-instance

Bmy-instance:us-central1:my-project

Cus-central1:my-project:my-instance

Dmy-project:my-instance:us-central1

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the order of project, region, and instance.

Using slashes or dots instead of colons.

The correct format for the instance connection name is project:region:instance.

2fill in blank

medium

Complete the command to specify the credentials file for Cloud SQL Proxy.

GCP

cloud_sql_proxy -instances=my-project:us-central1:my-instance=tcp:5432 -credential_file=[1]

Drag options to blanks, or click blank then click option'

A/path/to/key.json

B/path/to/key.txt

C/path/to/key.yaml

D/path/to/key.pem

Attempts:

3 left

💡 Hint

Common Mistakes

Using a text or YAML file instead of JSON.

Using a certificate file (.pem) instead of credentials.

The credentials file for Cloud SQL Proxy must be a JSON key file downloaded from the Google Cloud Console.

3fill in blank

hard

Fix the error in the command to run Cloud SQL Proxy on port 3306.

GCP

cloud_sql_proxy -instances=my-project:us-central1:my-instance=[1]

Drag options to blanks, or click blank then click option'

Atcp:3307

Btcp:3306

Cudp:3306

Dhttp:3306

Attempts:

3 left

💡 Hint

Common Mistakes

Using UDP or HTTP protocols instead of TCP.

Using the wrong port number.

Cloud SQL Proxy listens on TCP ports, so the correct prefix is tcp: followed by the port number.

4fill in blank

hard

Fill both blanks to create a command that runs Cloud SQL Proxy with instance connection and logs output to a file.

GCP

cloud_sql_proxy -instances=[1]=tcp:5432 > [2] 2>&1 &

Drag options to blanks, or click blank then click option'

Amy-project:us-central1:my-instance

Bproxy.log

Cerror.log

Dmy-instance:us-central1:my-project

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping project and instance in the connection name.

Using a non-log file name for output.

The instance connection name must be in the correct format, and the log file is commonly named proxy.log.

5fill in blank

hard

Fill all three blanks to create a Python dictionary comprehension that maps instance names to their ports if the port is greater than 5000.

GCP

ports = { [1]: [2] for [1], [2] in instances if [2] > 5000 }

Drag options to blanks, or click blank then click option'

Ainstance

Bport

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names inconsistently.

Using the key variable in the condition instead of the value.

The variable instance is used as the key, and port as the value and in the condition.

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