Cloud SQL pricing in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Cloud SQL instance tier for pricing calculation.

GCP

instance_config = {"tier": "[1]"}

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

Adb-n1-standard-1

Bdb-custom-2-7680

Cdb-f1-micro

Ddb-n2-highmem-4

Attempts:

3 left

💡 Hint

Common Mistakes

Using a tier name that is not valid or does not exist.

Confusing custom machine types with predefined tiers.

The tier db-f1-micro is a valid Cloud SQL instance tier used for pricing and configuration.

2fill in blank

medium

Complete the code to set the storage type for Cloud SQL pricing.

GCP

storage_config = {"storageType": "[1]"}

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

ARAM

BSSD

CNVMe

DHDD

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing unsupported storage types like NVMe or RAM.

Confusing storage type with instance tier.

The storage type SSD is commonly used for Cloud SQL and affects pricing.

3fill in blank

hard

Fix the error in the code to correctly calculate the monthly cost for a Cloud SQL instance with 100 GB storage.

GCP

monthly_cost = instance_price_per_hour * 24 * 30 + [1] * storage_price_per_gb

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

A1000

B10

C1

D100

Attempts:

3 left

💡 Hint

Common Mistakes

Using 1000 instead of 100, which overestimates cost.

Using 10 or 1, which underestimates cost.

The storage size is 100 GB, so the multiplier must be 100 to calculate storage cost correctly.

4fill in blank

hard

Fill both blanks to define a Cloud SQL instance with 2 vCPUs and 7.5 GB RAM for pricing estimation.

GCP

instance_config = {"vCPU": [1], "memoryGb": [2]

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

A2

B4

C7.5

D15

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping vCPU and memory values.

Using incorrect numbers not matching the instance specs.

The instance has 2 vCPUs and 7.5 GB RAM, which are used for pricing calculations.

5fill in blank

hard

Fill all three blanks to calculate total monthly cost including instance, storage, and backup costs.

GCP

total_cost = ([1] * hours_per_month) + (storage_gb * [2]) + (backup_gb * [3])

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

Ainstance_price_per_hour

Bstorage_price_per_gb

Cbackup_price_per_gb

Dnetwork_price_per_gb

Attempts:

3 left

💡 Hint

Common Mistakes

Including network price instead of backup price.

Mixing up storage and backup price variables.

The total cost includes instance hourly price, storage price per GB, and backup price per GB.

Practice

1. Which factor does NOT directly affect the pricing of a Cloud SQL instance?

easy

A. The amount of network egress traffic

B. The amount of storage used

C. The size of the instance (CPU and RAM)

D. The number of users accessing the database

Solution

1. Step 1: Identify pricing factors for Cloud SQL

   Cloud SQL pricing depends on instance size, storage, backups, and network usage.

2. Step 2: Analyze the impact of users

   The number of users does not directly affect pricing; costs are based on resources used, not user count.

3. Final Answer:

   The number of users accessing the database -> Option D

4. Quick Check:

   Users do not affect pricing directly [OK]

Hint: Focus on resource usage, not user count, for pricing [OK]

Common Mistakes:

• Thinking more users always increase cost directly
• Confusing network traffic with user count
• Ignoring storage and instance size impact

2. Which of the following is the correct way to describe Cloud SQL pricing components?

easy

A. Pricing depends only on the number of database queries.

B. Pricing is fixed monthly regardless of usage.

C. Pricing is based on instance size, storage, backups, and network usage.

D. Pricing is based solely on the number of database users.

Solution

1. Step 1: Recall Cloud SQL pricing components

   Cloud SQL pricing includes instance size, storage, backups, and network usage.

2. Step 2: Compare options to pricing facts

   Only Pricing is based on instance size, storage, backups, and network usage. correctly lists the main pricing factors; others are incorrect or incomplete.

3. Final Answer:

   Pricing is based on instance size, storage, backups, and network usage. -> Option C

4. Quick Check:

   Pricing components = instance size, storage, backups, network [OK]

Hint: Remember pricing depends on resources, not fixed or query count [OK]

Common Mistakes:

• Assuming pricing is fixed monthly
• Confusing query count with pricing
• Ignoring backups and network costs

3. A Cloud SQL instance uses 4 vCPUs and 15 GB RAM, with 100 GB storage and 10 GB network egress. Which cost factor will likely be the highest contributor to the monthly bill?

medium

A. Instance size (CPU and RAM)

B. Storage

C. Network egress

D. Backups

Solution

1. Step 1: Analyze resource usage

   Instance size with 4 vCPUs and 15 GB RAM is a significant resource, usually costing more than storage or network for moderate usage.

2. Step 2: Compare other factors

   Storage of 100 GB and network egress of 10 GB are moderate; backups cost depends on backup size but usually less than instance size.

3. Final Answer:

   Instance size (CPU and RAM) -> Option A

4. Quick Check:

   Instance size usually costs most [OK]

Hint: Instance size usually dominates cost over storage and network [OK]

Common Mistakes:

• Overestimating network egress cost
• Ignoring instance size impact
• Assuming backups cost more than instance

4. You configured a Cloud SQL instance with 2 vCPUs and 7.5 GB RAM, but your monthly bill is unexpectedly high. Which of the following could be a likely cause?

medium

A. You set the instance size to 1 vCPU instead of 2.

B. You enabled automated backups with large backup storage.

C. You reduced network egress to zero.

D. You deleted all storage volumes.

Solution

1. Step 1: Identify possible cost causes

   Automated backups can increase storage costs significantly if backup size is large.

2. Step 2: Evaluate other options

   Setting instance size smaller reduces cost, reducing network egress lowers cost, deleting storage is not possible without data loss and would not increase cost.

3. Final Answer:

   You enabled automated backups with large backup storage. -> Option B

4. Quick Check:

   Backups can increase cost unexpectedly [OK]

Hint: Check backup storage size if bill is high unexpectedly [OK]

Common Mistakes:

• Assuming smaller instance size increases cost
• Ignoring backup storage impact
• Thinking deleting storage increases cost

5. You want to minimize your Cloud SQL monthly cost while maintaining performance. Which combination of actions is best?

hard

A. Choose an appropriate instance size, use balanced storage type, and schedule backups during off-peak hours.

B. Choose a larger instance size, use HDD storage, and disable backups.

C. Choose the smallest instance size, disable backups, and ignore network usage.

D. Choose a smaller instance size, use SSD storage, and enable automated backups.

Solution

1. Step 1: Balance instance size and storage

   Choosing an appropriate instance size and balanced storage optimizes cost and performance.

2. Step 2: Manage backups smartly

   Scheduling backups during off-peak hours reduces performance impact and controls costs without disabling backups.

3. Final Answer:

   Choose an appropriate instance size, use balanced storage type, and schedule backups during off-peak hours. -> Option A

4. Quick Check:

   Balance resources and backup timing for cost and performance [OK]

Hint: Balance size, storage, and backup timing for best cost [OK]

Common Mistakes:

• Choosing smallest instance ignoring performance
• Disabling backups risking data loss
• Ignoring storage type impact