Why Default VPC and subnets in GCP? - Purpose & Use Cases

The Big Idea

What if your cloud network was ready to use the moment you create your project?

The Scenario

Imagine you want to connect several computers in the cloud to talk to each other. You try to create the network and connections by hand every time you start a new project.

You have to pick IP addresses, set up routes, and make sure everything fits together perfectly.

The Problem

Doing this by hand takes a lot of time and is easy to mess up.

If you pick overlapping IP addresses or forget a route, your computers won't talk to each other.

It's like trying to build a road system without a map or plan.

The Solution

Default VPC and subnets give you a ready-made network that works out of the box.

You get a safe, organized space where your cloud computers can connect without extra setup.

This saves time and avoids mistakes.

Before vs After

✗ Before

Create network, assign IPs, add routes manually each time

✓ After

Use default VPC and subnets automatically created by GCP

What It Enables

You can start building cloud projects immediately without worrying about network setup.

Real Life Example

A developer launches a new app and uses the default VPC to connect servers instantly, skipping complex network setup.

Key Takeaways

Manual network setup is slow and error-prone.

Default VPC and subnets provide a ready network environment.

This lets you focus on your app, not the network details.

Practice

1. What is the Default VPC in Google Cloud Platform?

easy

A. A virtual machine template for quick deployment

B. A custom network you must create manually before use

C. A storage bucket for default files

D. A pre-made network with one subnet per region and default IP ranges

Solution

1. Step 1: Understand the Default VPC concept

   The Default VPC is a network automatically created by GCP to help users start quickly without manual setup.

2. Step 2: Identify its features

   It includes one subnet in each region with default IP address ranges, ready for use.

3. Final Answer:

   A pre-made network with one subnet per region and default IP ranges -> Option D

4. Quick Check:

   Default VPC = Pre-made network with subnets [OK]

Hint: Default VPC is ready-made with subnets in all regions [OK]

Common Mistakes:

• Thinking Default VPC is a VM or storage
• Assuming you must create it manually
• Confusing it with custom networks

2. Which gcloud command lists the subnets in the Default VPC?

easy

A. gcloud compute networks subnets list --network=default

B. gcloud compute networks list

C. gcloud compute instances list

D. gcloud storage buckets list

Solution

1. Step 1: Identify the command to list subnets

   The command to list subnets requires 'compute networks subnets list' with a network filter.

2. Step 2: Specify the Default VPC network

   Using '--network=default' filters subnets belonging to the Default VPC.

3. Final Answer:

   gcloud compute networks subnets list --network=default -> Option A

4. Quick Check:

   List subnets in default network = gcloud compute networks subnets list --network=default [OK]

Hint: Use 'subnets list' with --network=default to see Default VPC subnets [OK]

Common Mistakes:

• Using 'networks list' which shows networks, not subnets
• Listing instances or storage buckets instead
• Omitting the network filter

3. Given the Default VPC has a subnet in us-central1 with IP range 10.128.0.0/20, what is the total number of usable IP addresses in this subnet?

medium

A. 4096 usable IP addresses

B. 4091 usable IP addresses

C. 4094 usable IP addresses

D. 4090 usable IP addresses

Solution

1. Step 1: Calculate total IPs in a /20 subnet

   A /20 subnet has 2^(32-20) = 4096 total IP addresses.

2. Step 2: Subtract reserved IPs in GCP subnet

   GCP reserves 5 IPs per subnet (network, gateway, broadcast, and two reserved), so usable IPs = 4096 - 5 = 4091.

3. Final Answer:

   4091 usable IP addresses -> Option B

4. Quick Check:

   /20 subnet usable IPs = 4091 [OK]

Hint: Subtract 5 reserved IPs from total in subnet range [OK]

Common Mistakes:

• Using total IPs without subtracting reserved ones
• Confusing subnet mask with number of IPs
• Ignoring GCP reserved IP addresses

4. You try to create a new subnet in the Default VPC with IP range 10.128.0.0/20 but get an error. What is the most likely cause?

medium

A. The IP range overlaps with an existing Default VPC subnet

B. The Default VPC does not allow adding subnets

C. The subnet name is invalid

D. The region is not specified

Solution

1. Step 1: Identify the type of Default VPC

   The Default VPC is an auto-mode VPC network where subnets are automatically created and managed by GCP.

2. Step 2: Understand limitations

   You cannot manually create additional subnets in an auto-mode VPC like the Default VPC.

3. Step 3: Reason about the error cause

   Trying to create a subnet with an IP range that overlaps an existing subnet in the Default VPC causes an error.

4. Final Answer:

   The IP range overlaps with an existing Default VPC subnet -> Option A

5. Quick Check:

   Subnet creation error due to overlapping IP range [OK]

Hint: Subnet creation fails if IP range overlaps existing subnet [OK]

Common Mistakes:

• Thinking IP range overlap is not the cause
• Assuming Default VPC allows manual subnets like custom VPCs
• Forgetting to specify region or using invalid name (different errors)

5. You want to create a custom VPC with subnets in three regions without overlapping IP ranges. Which approach best follows GCP best practices?

hard

A. Create multiple Default VPCs, one per region

B. Use the Default VPC and add subnets with overlapping IP ranges

C. Create a custom VPC and assign non-overlapping CIDR blocks for each subnet in different regions

D. Create subnets with the same IP range in different regions inside the same VPC

Solution

1. Step 1: Understand custom VPC subnet creation

   Custom VPCs allow you to define your own IP ranges and subnets per region.

2. Step 2: Avoid IP range overlap

   Assigning unique CIDR blocks per subnet prevents routing conflicts and follows best practices.

3. Step 3: Evaluate other options

   Default VPC cannot have overlapping subnets; multiple Default VPCs per project are not allowed; same IP ranges in one VPC cause conflicts.

4. Final Answer:

   Create a custom VPC and assign non-overlapping CIDR blocks for each subnet in different regions -> Option C

5. Quick Check:

   Custom VPC + unique CIDRs = Best practice [OK]

Hint: Use custom VPC with unique subnet IP ranges per region [OK]

Common Mistakes:

• Trying to add overlapping subnets to Default VPC
• Assuming multiple Default VPCs per project are possible
• Using same IP ranges in multiple subnets inside one VPC