Why managed databases matter in GCP - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why choose a managed database service?

Which of the following is the main benefit of using a managed database service like Google Cloud SQL instead of managing your own database on a virtual machine?

A You can avoid paying for the database service and only pay for storage.

B You get automatic backups, patching, and scaling without manual intervention.

C You have full control over the operating system and database software versions.

D You must manually configure replication and failover for high availability.

💡 Hint

Think about what tasks a managed service automates for you.

Managed database services handle backups, updates, and scaling automatically, reducing operational work and risk.

❓ service_behavior

intermediate

Behavior of managed database backups

What happens when you enable automated backups on a managed database instance in Google Cloud SQL?

A The service automatically creates daily backups and retains them for a configured period.

B Backups are created only when you manually trigger them from the console.

C Backups are stored only on the same disk as the database instance.

D Backups cause the database to shut down temporarily during the process.

💡 Hint

Consider how managed services handle backups to avoid downtime.

Managed databases create daily backups automatically and keep them for a set retention period without downtime.

❓ Architecture

advanced

High availability with managed databases

You want to design a highly available database setup using Google Cloud SQL. Which configuration best achieves this?

A Use a single primary instance with no replicas and rely on backups.

B Create two independent primary instances in the same zone without replication.

C Create a primary instance with a failover replica in a different zone.

D Manually copy data between two instances every hour.

💡 Hint

Think about how managed services provide automatic failover.

A failover replica in a different zone allows automatic failover if the primary fails, ensuring high availability.

❓ security

advanced

Security features of managed databases

Which security feature is typically provided by managed database services like Google Cloud SQL to protect data at rest?

A Storing data unencrypted to improve performance.

B Disabling all network access by default without exceptions.

C Requiring manual installation of encryption software on the VM.

D Automatic encryption of stored data using Google-managed keys.

💡 Hint

Consider how cloud providers protect stored data without user setup.

Managed databases encrypt data at rest automatically using keys managed by the cloud provider, enhancing security without user effort.

✅ Best Practice

expert

Cost optimization with managed databases

You want to optimize costs for a managed database that has variable workloads with peak times and idle times. Which approach best balances cost and performance?

A Use a managed database with autoscaling enabled to adjust resources based on demand.

B Provision the largest instance size permanently to handle peak loads at all times.

C Manually stop the database instance during idle times to save costs.

D Use multiple small instances without load balancing to distribute workload.

💡 Hint

Think about how managed services can adjust resources automatically.

Autoscaling allows the database to increase resources during peak demand and reduce them when idle, saving costs while maintaining performance.

Practice

1. Why do many companies prefer managed databases over self-managed databases in the cloud?

easy

A. Because managed databases always cost less than self-managed ones

B. Because managed databases require manual hardware setup

C. Because managed databases do not support automatic failover

D. Because managed databases handle backups, updates, and scaling automatically

Solution

1. Step 1: Understand managed database features

   Managed databases provide automatic backups, updates, and scaling without user intervention.

2. Step 2: Compare with self-managed databases

   Self-managed databases require manual setup and maintenance, which is more complex and error-prone.

3. Final Answer:

   Because managed databases handle backups, updates, and scaling automatically -> Option D

4. Quick Check:

   Managed databases automate maintenance = A [OK]

Hint: Managed means automatic maintenance and scaling [OK]

Common Mistakes:

• Thinking managed databases need manual hardware setup
• Assuming managed databases lack failover support
• Believing managed databases always cost less

2. Which of the following is the correct way to create a managed Cloud SQL instance using gcloud CLI?

easy

A. gcloud sql instances create my-instance --tier=db-f1-micro --region=us-central1

B. gcloud sql create instance my-instance --size=small --zone=us-central1-a

C. gcloud sql instances new my-instance --machine=db-n1-standard-1

D. gcloud sql setup my-instance --type=managed --region=us-central1

Solution

1. Step 1: Identify correct gcloud command syntax

   The correct command to create a Cloud SQL instance is 'gcloud sql instances create' with tier and region flags.

2. Step 2: Check each option for syntax correctness

   gcloud sql instances create my-instance --tier=db-f1-micro --region=us-central1 matches the official syntax; others use incorrect verbs or flags.

3. Final Answer:

   gcloud sql instances create my-instance --tier=db-f1-micro --region=us-central1 -> Option A

4. Quick Check:

   Correct gcloud create syntax = B [OK]

Hint: Use 'gcloud sql instances create' to make managed instances [OK]

Common Mistakes:

• Using 'create instance' instead of 'instances create'
• Wrong flags like --size or --machine
• Confusing region and zone flags

3. Consider this code snippet using Google Cloud SDK to create a managed database instance:

gcloud sql instances create test-db --tier=db-n1-standard-1 --region=us-east1

What will happen if you run this command twice with the same instance name?

medium

A. The second command will fail with an error about duplicate instance

B. The second command will update the existing instance

C. The second command will create a new instance with a suffix

D. The second command will delete the first instance and create a new one

Solution

1. Step 1: Understand instance naming rules in Cloud SQL

   Instance names must be unique. Creating an instance with an existing name causes an error.

2. Step 2: Predict behavior on duplicate creation

   Running the create command again with the same name results in a failure due to name conflict.

3. Final Answer:

   The second command will fail with an error about duplicate instance -> Option A

4. Quick Check:

   Duplicate instance name causes error = A [OK]

Hint: Duplicate instance names cause errors, not updates [OK]

Common Mistakes:

• Assuming the instance updates automatically
• Thinking a new instance with suffix is created
• Believing the old instance is deleted automatically

4. You tried to create a managed Cloud SQL instance but got an error: "Invalid tier specified." What is the most likely cause?

medium

A. You did not enable the Cloud SQL API

B. You used a tier name that does not exist or is misspelled

C. You used a valid tier but invalid instance name

D. You forgot to specify the region

Solution

1. Step 1: Analyze the error message

   The error "Invalid tier specified" indicates the tier value is incorrect or unrecognized.

2. Step 2: Identify common causes

   Misspelling or using a non-existent tier causes this error, not missing region or API enablement.

3. Final Answer:

   You used a tier name that does not exist or is misspelled -> Option B

4. Quick Check:

   Invalid tier error means wrong tier name = D [OK]

Hint: Check tier spelling and availability first [OK]

Common Mistakes:

• Assuming missing region causes tier error
• Thinking API enablement causes tier error
• Ignoring typo in tier name

5. You want to ensure your managed Cloud SQL database automatically recovers from hardware failures without manual intervention. Which feature should you enable?

hard

A. Read replicas for reporting only

B. Manual backups scheduled daily

C. High availability with automatic failover

D. Custom machine types for performance tuning

Solution

1. Step 1: Identify the feature for automatic recovery

   High availability with automatic failover ensures the database switches to a standby instance if hardware fails.

2. Step 2: Evaluate other options

   Manual backups do not provide automatic recovery; read replicas are for scaling reads; custom machines tune performance but not recovery.

3. Final Answer:

   High availability with automatic failover -> Option C

4. Quick Check:

   Automatic failover = automatic recovery [OK]

Hint: Enable automatic failover for no-downtime recovery [OK]

Common Mistakes:

• Confusing backups with automatic failover
• Using read replicas for failover
• Thinking custom machines handle recovery