Creating a Cloud SQL instance in GCP - Practice Exercises

Challenge - 5 Problems

❓ Configuration

intermediate

Identify the correct gcloud command to create a MySQL Cloud SQL instance

You want to create a MySQL Cloud SQL instance named my-instance in the us-central1 region with 10GB storage. Which gcloud command will do this correctly?

A gcloud sql instances create my-instance --database-version=POSTGRES_13 --tier=db-f1-micro --region=us-central1 --storage-size=10

B gcloud sql instances create my-instance --database-version=MYSQL_8_0 --tier=db-f1-micro --region=us-central1 --storage-size=10

C gcloud sql instances create my-instance --database-version=MYSQL_5_7 --tier=db-n1-standard-1 --region=us-central1 --storage-size=10

D gcloud sql instances create my-instance --database-version=MYSQL_8_0 --tier=db-f1-micro --region=us-east1 --storage-size=20

💡 Hint

Check the database version, region, and storage size carefully.

Option B correctly specifies MySQL 8.0, the region us-central1, and 10GB storage. Option B uses PostgreSQL, not MySQL. Option B uses MySQL 5.7 and a zone instead of region. Option B uses the wrong region and storage size.

❓ Architecture

intermediate

Choose the best architecture for high availability with Cloud SQL

You want to deploy a Cloud SQL instance that remains available even if one zone fails. Which architecture option achieves this?

A Create a single Cloud SQL instance in one zone with automated backups enabled.

B Create two separate Cloud SQL instances in different regions and manually switch between them.

C Create a Cloud SQL instance with high availability (HA) enabled, which creates a primary and standby instance in different zones.

D Create a Cloud SQL instance with read replicas in the same zone.

💡 Hint

Think about automatic failover and zone redundancy.

Option C enables high availability with automatic failover between zones. Option C has no failover. Option C requires manual switching and is complex. Option C read replicas do not provide failover for writes.

❓ security

advanced

Determine the correct way to restrict access to a Cloud SQL instance

You want to allow only your Compute Engine VM instances in the default network to connect to your Cloud SQL instance. Which method correctly restricts access?

A Add the VM instances' internal IP addresses to the Cloud SQL instance's authorized networks.

B Disable all authorized networks and allow connections from any IP.

C Add the VM instances' external IP addresses to the Cloud SQL instance's authorized networks.

D Enable the Cloud SQL instance's private IP and ensure the VM instances are in the same VPC network.

💡 Hint

Consider private IP connectivity within the same network.

Option D uses private IP, which restricts access to VMs in the same VPC network securely. Option D is invalid because internal IPs are not used in authorized networks. Option D exposes the instance to external IPs, less secure. Option D allows all IPs, no restriction.

❓ service_behavior

advanced

Predict the behavior when deleting a Cloud SQL instance with automated backups enabled

You delete a Cloud SQL instance that has automated backups enabled. What happens to the backups?

A Automated backups are retained for the backup retention period and can be used to restore a new instance.

B Backups are converted to manual backups and remain indefinitely.

C All automated backups are deleted immediately along with the instance.

D Backups are archived to Cloud Storage and billed separately.

💡 Hint

Think about backup retention policies after instance deletion.

Option A is correct because automated backups are retained for the configured retention period and can be used to restore a new instance. Option A deletes backups immediately, which is incorrect. Option A is not how backups behave. Option A is not the backup storage method.

✅ Best Practice

expert

Select the best practice for managing Cloud SQL instance maintenance windows

You want to minimize downtime during maintenance for your Cloud SQL instance. Which approach follows best practice?

A Configure the maintenance window to a low-traffic period when your application usage is minimal.

B Set the maintenance window to a random time during the day to avoid peak hours.

C Disable maintenance windows to prevent any automatic updates or restarts.

D Schedule maintenance windows during peak hours to ensure quick updates.

💡 Hint

Consider when your users are least active.

Option A is best practice because scheduling maintenance during low-traffic periods reduces user impact. Option A is random and may cause downtime during busy times. Option A is not allowed as maintenance is required. Option A increases user disruption.

Practice

1. What is the main purpose of creating a Cloud SQL instance in Google Cloud?

easy

A. To store files and objects in the cloud

B. To set up a managed database service without handling server maintenance

C. To create a virtual machine for running applications

D. To configure network firewalls for security

Solution

1. Step 1: Understand Cloud SQL service

   Cloud SQL is a managed database service that handles database setup and maintenance for you.

2. Step 2: Identify the purpose of creating an instance

   Creating a Cloud SQL instance means setting up a database server managed by Google Cloud, so you don't manage the server yourself.

3. Final Answer:

   To set up a managed database service without handling server maintenance -> Option B

4. Quick Check:

   Cloud SQL = Managed database service [OK]

Hint: Cloud SQL means managed database, not VM or storage [OK]

Common Mistakes:

• Confusing Cloud SQL with virtual machines
• Thinking Cloud SQL is for file storage
• Mixing Cloud SQL with network configuration

2. Which of the following is the correct command to create a Cloud SQL instance named my-instance with MySQL version 8.0 in the region us-central1?

easy

A. gcloud sql instances create my-instance --database-version=MYSQL_8_0 --region=us-central1

B. gcloud sql create instance my-instance --version=MYSQL8 --location=us-central1

C. gcloud sql instances new my-instance --db-version=8.0 --zone=us-central1

D. gcloud sql instances create my-instance --db-version=MYSQL8 --region=us-central1

Solution

1. Step 1: Recall correct gcloud command syntax

   The correct command starts with gcloud sql instances create followed by the instance name.

2. Step 2: Check flags for database version and region

   The flag for database version is --database-version and for region is --region. The version value for MySQL 8.0 is MYSQL_8_0.

3. Final Answer:

   gcloud sql instances create my-instance --database-version=MYSQL_8_0 --region=us-central1 -> Option A

4. Quick Check:

   Correct flags and syntax = gcloud sql instances create my-instance --database-version=MYSQL_8_0 --region=us-central1 [OK]

Hint: Use --database-version and --region flags exactly [OK]

Common Mistakes:

• Using incorrect flag names like --version or --db-version
• Swapping region flag with zone
• Wrong command order or missing 'instances create'

3. What will be the output of the following command if executed successfully?

gcloud sql instances create test-instance --database-version=POSTGRES_14 --tier=db-f1-micro --region=us-east1

medium

A. An error because tier db-f1-micro is not supported

B. An error because region us-east1 is invalid

C. A new Cloud SQL instance with MySQL 14 in us-east1 region

D. A new Cloud SQL instance named test-instance with PostgreSQL 14 in us-east1 region

Solution

1. Step 1: Analyze command parameters

   The command creates a Cloud SQL instance named test-instance with PostgreSQL version 14, machine tier db-f1-micro, in region us-east1.

2. Step 2: Validate parameters

   db-f1-micro is a valid machine tier for small instances, us-east1 is a valid region, and POSTGRES_14 is a valid database version.

3. Final Answer:

   A new Cloud SQL instance named test-instance with PostgreSQL 14 in us-east1 region -> Option D

4. Quick Check:

   Valid flags and values create instance = A new Cloud SQL instance named test-instance with PostgreSQL 14 in us-east1 region [OK]

Hint: Check database version and tier validity carefully [OK]

Common Mistakes:

• Confusing PostgreSQL with MySQL versions
• Assuming db-f1-micro is invalid tier
• Mistaking region names

4. You tried to create a Cloud SQL instance with this command:

gcloud sql instances create mydb --database-version=MYSQL_5_7 --tier=n1-standard-1 --region=us-west1

But you get an error saying the tier is invalid. What is the likely cause?

medium

A. The tier name is correct but the database version is invalid

B. The region us-west1 does not support MySQL 5.7

C. The tier name should be db-n1-standard-1 with 'db-' prefix

D. The tier name requires a different format for MySQL

Solution

1. Step 1: Check tier naming conventions

   Cloud SQL machine tiers use the 'db-' prefix. The correct tier name is 'db-n1-standard-1'.

2. Step 2: Validate other parameters

   MySQL 5.7 is valid, and us-west1 supports it. The error is due to missing 'db-' prefix in tier name.

3. Final Answer:

   The tier name should be db-n1-standard-1 with 'db-' prefix -> Option C

4. Quick Check:

   Tier names include 'db-' prefix [OK]

Hint: Add 'db-' prefix to tier names for Cloud SQL [OK]

Common Mistakes:

• Omitting 'db-' prefix in tier names
• Assuming region limits cause tier errors
• Mixing database version errors with tier errors

5. You want to create a highly available Cloud SQL instance with PostgreSQL 13 in region us-central1. Which command correctly sets up a primary instance with high availability enabled?

hard

A. gcloud sql instances create ha-instance --database-version=POSTGRES_13 --region=us-central1 --availability-type=REGIONAL

B. gcloud sql instances create ha-instance --database-version=POSTGRES_13 --region=us-central1 --high-availability

C. gcloud sql instances create ha-instance --database-version=POSTGRES_13 --region=us-central1 --availability=HIGH

D. gcloud sql instances create ha-instance --database-version=POSTGRES_13 --region=us-central1 --replica-type=PRIMARY

Solution

1. Step 1: Identify flag for high availability

   The correct flag to enable high availability in Cloud SQL is --availability-type=REGIONAL.

2. Step 2: Confirm other parameters

   Database version POSTGRES_13 and region us-central1 are valid. The command uses correct syntax for creating a highly available instance.

3. Final Answer:

   gcloud sql instances create ha-instance --database-version=POSTGRES_13 --region=us-central1 --availability-type=REGIONAL -> Option A

4. Quick Check:

   Use --availability-type=REGIONAL for HA [OK]

Hint: Use --availability-type=REGIONAL to enable high availability [OK]

Common Mistakes:

• Using non-existent flags like --high-availability
• Confusing replica-type with availability
• Using incorrect availability flag names