Subnet modes (auto, custom) in GCP - Time & Space Complexity

Time Complexity: Subnet modes (auto, custom)

O(n)

Understanding Time Complexity

When creating networks in GCP, subnet modes control how many subnetworks are made automatically or manually.

We want to know how the number of subnetworks affects the work GCP does behind the scenes.

Scenario Under Consideration

Analyze the time complexity of creating subnetworks in different modes.

# Create a network in auto mode
gcloud compute networks create my-auto-network --subnet-mode=auto

# Create a network in custom mode
gcloud compute networks create my-custom-network --subnet-mode=custom

# Add subnets manually in custom mode
for i in {1..n}; do
  gcloud compute networks subnets create subnet-$i --network=my-custom-network --region=us-central1 --range=10.0.$i.0/24
done

This sequence shows creating a network with automatic subnet creation versus manual subnet creation one by one.

Identify Repeating Operations

Look at what actions happen multiple times.

• Primary operation: Creating subnetworks (API calls to create subnets)
• How many times: In auto mode, subnets are created once automatically for each region; in custom mode, each subnet creation is a separate call repeated n times.

How Execution Grows With Input

As the number of subnetworks (n) increases, the number of subnet creation calls grows.

Input Size (n)	Approx. API Calls/Operations
10	10 subnet creation calls in custom mode; 1 in auto mode
100	100 subnet creation calls in custom mode; 1 in auto mode
1000	1000 subnet creation calls in custom mode; 1 in auto mode

Pattern observation: Custom mode scales linearly with the number of subnets; auto mode does not increase calls with subnet count.

Final Time Complexity

Time Complexity: O(n)

This means the work grows directly with how many subnets you create manually in custom mode.

Common Mistake

[X] Wrong: "Creating many subnets in custom mode is as fast as auto mode because GCP handles it."

[OK] Correct: Each subnet creation is a separate action, so more subnets mean more work and time.

Interview Connect

Understanding how resource creation scales helps you design efficient cloud networks and explain your choices clearly.

Self-Check

"What if we batch subnet creations in custom mode using scripts or APIs? How would the time complexity change?"

Practice

1. What happens when you create a VPC network in auto subnet mode in GCP?

easy

A. Subnets are automatically created in all regions with predefined IP ranges.

B. No subnets are created; you must create them manually.

C. Only one subnet is created in the default region.

D. Subnets are created but without any IP ranges assigned.

Solution

1. Step 1: Understand auto subnet mode behavior

   In auto mode, GCP automatically creates subnets in every region with default IP ranges.

2. Step 2: Compare with other modes

   Unlike custom mode, auto mode does not require manual subnet creation or IP range assignment.

3. Final Answer:

   Subnets are automatically created in all regions with predefined IP ranges. -> Option A

4. Quick Check:

   Auto mode = automatic subnet creation [OK]

Hint: Auto mode means automatic subnets in all regions [OK]

Common Mistakes:

• Thinking auto mode requires manual subnet creation
• Assuming only one subnet is created
• Believing subnets have no IP ranges assigned

2. Which of the following is the correct way to create a custom subnet in GCP using gcloud CLI?

easy

A. gcloud compute networks subnets create my-network --subnet-mode=custom

B. gcloud compute networks create my-network --subnet-mode=auto

C. gcloud compute networks create my-subnet --range=10.0.0.0/24

D. gcloud compute networks subnets create my-subnet --network=my-network --range=10.0.0.0/24

Solution

1. Step 1: Identify command to create a subnet

   The command to create a subnet is gcloud compute networks subnets create with network and IP range specified.

2. Step 2: Check option correctness

   gcloud compute networks subnets create my-subnet --network=my-network --range=10.0.0.0/24 correctly uses the subnet creation command with network and IP range parameters.

3. Final Answer:

   gcloud compute networks subnets create my-subnet --network=my-network --range=10.0.0.0/24 -> Option D

4. Quick Check:

   Subnet creation uses 'networks subnets create' with range [OK]

Hint: Use 'networks subnets create' with --range for custom subnets [OK]

Common Mistakes:

• Using 'networks create' to create subnets
• Missing the --range parameter for IP range
• Confusing network and subnet names

3. Given a VPC network in custom subnet mode with two subnets:
subnet-a: 10.1.0.0/16
subnet-b: 10.2.0.0/16
What happens if you try to create a third subnet with IP range 10.1.128.0/17?

medium

A. The subnet is created successfully without issues.

B. The subnet is created but traffic is blocked between subnets.

C. Creation fails due to overlapping IP ranges with subnet-a.

D. The subnet is created but assigned a different IP range automatically.

Solution

1. Step 1: Check IP range overlap

   Subnet-a uses 10.1.0.0/16 which covers 10.1.0.0 to 10.1.255.255. The new subnet 10.1.128.0/17 overlaps this range.

2. Step 2: Understand subnet creation rules

   GCP does not allow overlapping IP ranges in subnets within the same VPC network.

3. Final Answer:

   Creation fails due to overlapping IP ranges with subnet-a. -> Option C

4. Quick Check:

   Overlapping IP ranges cause subnet creation failure [OK]

Hint: Check IP ranges for overlap before subnet creation [OK]

Common Mistakes:

• Assuming subnets can overlap IP ranges
• Thinking GCP auto-adjusts overlapping ranges
• Believing traffic is blocked but subnet created

4. You created a VPC network in custom subnet mode but forgot to create any subnets. What is the result when you try to deploy a VM instance in this network?

medium

A. The VM instance deploys successfully with an automatic subnet created.

B. The VM deployment fails because no subnet exists in the network.

C. The VM deploys but without an internal IP address.

D. The VM deploys but is not reachable from other resources.

Solution

1. Step 1: Understand custom subnet mode requirements

   In custom mode, subnets must be created manually before deploying resources.

2. Step 2: Check VM deployment dependency

   VMs require a subnet to get an IP address; without subnets, deployment fails.

3. Final Answer:

   The VM deployment fails because no subnet exists in the network. -> Option B

4. Quick Check:

   Custom mode needs subnets before VM deployment [OK]

Hint: No subnet means VM deployment fails in custom mode [OK]

Common Mistakes:

• Assuming auto subnet creation in custom mode
• Thinking VM can deploy without internal IP
• Believing VM deploys but is unreachable

5. You want to create a VPC network that spans multiple regions with subnets having specific IP ranges you control. Which subnet mode should you choose and why?

hard

A. Custom mode, because it lets you manually create subnets with specific IP ranges in each region.

B. Custom mode, because it automatically creates subnets in all regions with default IP ranges.

C. Auto mode, because it allows you to edit IP ranges after subnet creation.

D. Auto mode, because it creates subnets automatically with your chosen IP ranges.

Solution

1. Step 1: Identify requirement for specific IP ranges

   You want control over IP ranges, so automatic default ranges won't work.

2. Step 2: Choose subnet mode matching control needs

   Custom mode allows manual subnet creation with chosen IP ranges per region.

3. Step 3: Eliminate incorrect options

   Auto mode does not allow choosing IP ranges; it creates default subnets automatically.

4. Final Answer:

   Custom mode, because it lets you manually create subnets with specific IP ranges in each region. -> Option A

5. Quick Check:

   Custom mode = manual subnet creation with chosen IP ranges [OK]

Hint: Custom mode for manual subnets with specific IP ranges [OK]

Common Mistakes:

• Confusing auto mode as allowing custom IP ranges
• Thinking auto mode subnets can be edited after creation
• Believing custom mode auto-creates subnets