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.