Cloud SQL pricing in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Cloud SQL Instance Pricing Components

Which of the following components directly affect the cost of a Cloud SQL instance in Google Cloud?

A Number of tables, number of indexes, and database engine type

B CPU count, memory size, storage capacity, and network egress

C Number of users connected, database schema size, and query complexity

D Operating system version, database engine version, and backup frequency

💡 Hint

Think about what resources you pay for when running a virtual machine and storage in the cloud.

Cloud SQL pricing is based on the resources allocated: CPU, memory, storage, and network usage. User count or schema details do not directly affect pricing.

❓ service_behavior

intermediate

Effect of Storage Type on Cloud SQL Pricing

You choose between SSD and HDD storage for your Cloud SQL instance. How does this choice affect your monthly bill?

A SSD storage costs more per GB than HDD storage, increasing your monthly bill

B HDD storage costs more per GB than SSD storage, increasing your monthly bill

C Both SSD and HDD storage cost the same per GB, so no price difference

D Storage type does not affect pricing; only storage size matters

💡 Hint

Think about performance differences and typical cloud storage pricing.

SSD storage offers faster performance but costs more per GB than HDD storage in Cloud SQL.

❓ Architecture

advanced

Cost Impact of High Availability Configuration in Cloud SQL

You enable High Availability (HA) for your Cloud SQL instance. What is the expected effect on your monthly cost?

A Monthly cost increases by 10% due to backup overhead

B Monthly cost decreases due to optimized resource usage

C Monthly cost stays the same because HA is free

D Monthly cost roughly doubles because a standby instance runs in another zone

💡 Hint

Consider what happens behind the scenes when HA is enabled.

HA creates a standby instance in a different zone, effectively doubling the compute and memory resources billed.

❓ security

advanced

Cost Considerations for Automated Backups in Cloud SQL

How do automated backups affect your Cloud SQL monthly bill?

A Backups reduce your monthly bill by compressing data

B Backups are included free with the instance storage

C Backup storage beyond the instance's allocated storage is billed separately

D Backup costs are fixed and do not depend on backup size

💡 Hint

Think about where backups are stored and how storage is billed.

Backup storage exceeding the instance's allocated storage is charged separately, increasing costs.

✅ Best Practice

expert

Optimizing Cloud SQL Costs for Variable Workloads

You have a Cloud SQL instance with variable workload peaks during the day and low usage at night. Which approach best optimizes cost without losing availability?

A Use Cloud SQL instance resizing to scale CPU and memory up during peaks and down at night

B Keep a large instance running 24/7 to handle peak loads without changes

C Delete the instance at night and recreate it in the morning

D Use only HDD storage to reduce costs regardless of workload

💡 Hint

Think about how to match resource allocation to demand dynamically.

Resizing the instance to match workload peaks and lows saves cost while maintaining availability. Deleting the instance causes downtime. HDD storage reduces cost but may hurt performance during peaks.