Why VPC provides network isolation in GCP - See It in Action

Why VPC Provides Network Isolation

📖 Scenario: You are setting up a cloud network for a small company. You want to keep different teams' resources separate so they don't interfere with each other.

🎯 Goal: Build a simple representation of a Virtual Private Cloud (VPC) network that shows how network isolation works by separating resources into different subnets.

📋 What You'll Learn

Create a dictionary called vpc_network with two subnets named exactly 'team_alpha' and 'team_beta'

Add a configuration variable called isolation_enabled set to True

Write a function called check_isolation that takes two subnet names and returns True if isolation_enabled is True and the subnets are different

Add a final line that calls check_isolation with 'team_alpha' and 'team_beta' and stores the result in network_isolated

💡 Why This Matters

🌍 Real World

Cloud providers use VPCs to keep different teams or projects' resources separate and secure, preventing accidental or malicious access.

💼 Career

Understanding VPC isolation is essential for cloud engineers and architects to design secure and well-organized cloud networks.

1

Create the VPC network with two subnets

Create a dictionary called vpc_network with two keys: 'team_alpha' and 'team_beta'. Each key should map to a list of IP addresses as strings. Use ['10.0.1.1', '10.0.1.2'] for 'team_alpha' and ['10.0.2.1', '10.0.2.2'] for 'team_beta'.

GCP

# Your code here

Hint

Think of vpc_network as a map with two separate areas for each team.

2

Add a configuration variable for isolation

Add a variable called isolation_enabled and set it to True to represent that network isolation is active.

GCP

vpc_network = {
    'team_alpha': ['10.0.1.1', '10.0.1.2'],
    'team_beta': ['10.0.2.1', '10.0.2.2']
}
# Your code here

Hint

This variable controls if the network keeps teams separate.

3

Write a function to check network isolation

Write a function called check_isolation that takes two parameters: subnet1 and subnet2. The function should return True if isolation_enabled is True and the two subnets are different. Otherwise, return False.

GCP

vpc_network = {
    'team_alpha': ['10.0.1.1', '10.0.1.2'],
    'team_beta': ['10.0.2.1', '10.0.2.2']
}
isolation_enabled = True
# Your code here

Hint

This function compares two subnets and uses the isolation setting to decide if they are isolated.

4

Check if the two subnets are isolated

Call the function check_isolation with arguments 'team_alpha' and 'team_beta'. Store the result in a variable called network_isolated.

GCP

vpc_network = {
    'team_alpha': ['10.0.1.1', '10.0.1.2'],
    'team_beta': ['10.0.2.1', '10.0.2.2']
}
isolation_enabled = True

def check_isolation(subnet1, subnet2):
    if isolation_enabled and subnet1 != subnet2:
        return True
    else:
        return False
# Your code here

Hint

This final step shows how to use the function to confirm network isolation.

Practice

1. What is the main reason a VPC provides network isolation in GCP?

easy

A. It allows unlimited public internet access.

B. It automatically encrypts all data in the cloud.

C. It shares IP addresses with other VPCs.

D. It creates a private network space separate from other users.

Solution

1. Step 1: Understand what a VPC is

   A VPC (Virtual Private Cloud) is a private network space in the cloud that you control.

2. Step 2: Identify how isolation is achieved

   Because the VPC is private, it separates your resources from others, preventing unwanted access.

3. Final Answer:

   It creates a private network space separate from other users. -> Option D

4. Quick Check:

   Private network space = Isolation [OK]

Hint: VPC means private network space, so it isolates [OK]

Common Mistakes:

• Thinking VPC automatically encrypts all data
• Assuming VPC allows open internet access
• Believing IP addresses are shared across VPCs

2. Which of the following is the correct way to define a subnet inside a VPC in GCP?

easy

A. subnets: [{name: 'subnet-1', cidr: '10.0.0.0/24'}]

B. subnetworks: [{name: 'subnet-1', ipRange: '10.0.0.0/24'}]

C. subnetworks: [{name: 'subnet-1', ipCidrRange: '10.0.0.0/24'}]

D. networks: [{subnet: 'subnet-1', range: '10.0.0.0/24'}]

Solution

1. Step 1: Recall GCP subnet syntax

   In GCP, subnets are defined with 'subnetworks' and use 'ipCidrRange' for the IP range.

2. Step 2: Match correct keys

   subnetworks: [{name: 'subnet-1', ipCidrRange: '10.0.0.0/24'}] uses 'subnetworks' and 'ipCidrRange', which is correct syntax.

3. Final Answer:

   subnetworks: [{name: 'subnet-1', ipCidrRange: '10.0.0.0/24'}] -> Option C

4. Quick Check:

   Correct keys = subnetworks: [{name: 'subnet-1', ipCidrRange: '10.0.0.0/24'}] [OK]

Hint: Look for 'ipCidrRange' key in subnet definition [OK]

Common Mistakes:

• Using 'ipRange' instead of 'ipCidrRange'
• Using 'subnets' instead of 'subnetworks'
• Mixing 'networks' and 'subnet' keys incorrectly

3. Given two VPCs with no peering, what happens if a VM in VPC A tries to ping a VM in VPC B?

medium

A. The ping fails because VPCs are isolated by default.

B. The ping fails unless firewall rules allow it.

C. The ping succeeds only if both VMs have public IPs.

D. The ping succeeds because all VPCs share the same network.

Solution

1. Step 1: Understand default VPC isolation

   By default, VPCs are isolated and cannot communicate without peering or VPN.

2. Step 2: Analyze ping behavior

   Since no peering exists, ping from VPC A to VPC B fails regardless of firewall rules.

3. Final Answer:

   The ping fails because VPCs are isolated by default. -> Option A

4. Quick Check:

   Default isolation blocks ping = The ping fails because VPCs are isolated by default. [OK]

Hint: No peering means no communication between VPCs [OK]

Common Mistakes:

• Assuming all VPCs share network by default
• Thinking firewall rules alone enable cross-VPC ping
• Believing public IPs allow ping without routing

4. You created two subnets in the same VPC but cannot connect VMs between them. What is the most likely cause?

medium

A. Firewall rules block traffic between the subnets.

B. Subnets must be in different VPCs to communicate.

C. VPCs do not allow communication between subnets.

D. VMs need public IPs to connect inside a VPC.

Solution

1. Step 1: Recall subnet communication in a VPC

   Subnets in the same VPC can communicate by default unless blocked.

2. Step 2: Identify cause of blocked communication

   Firewall rules can block traffic between subnets even inside the same VPC.

3. Final Answer:

   Firewall rules block traffic between the subnets. -> Option A

4. Quick Check:

   Firewall blocks = no subnet communication [OK]

Hint: Check firewall rules first when subnets can't connect [OK]

Common Mistakes:

• Thinking subnets in same VPC can't communicate
• Assuming VMs need public IPs for internal traffic
• Believing subnets must be in different VPCs

5. You want to isolate two teams' resources in the same GCP project. Which approach best uses VPC features to provide network isolation?

hard

A. Use one VPC with shared subnets and rely on firewall rules only.

B. Create two separate VPCs, one for each team, with no peering.

C. Assign public IPs to all VMs and use external firewalls.

D. Create one VPC and connect all resources with default routes.

Solution

1. Step 1: Understand isolation needs

   To isolate teams, separate network spaces are best to avoid accidental access.

2. Step 2: Evaluate VPC options

   Creating separate VPCs with no peering ensures strong isolation by default.

3. Final Answer:

   Create two separate VPCs, one for each team, with no peering. -> Option B

4. Quick Check:

   Separate VPCs = best isolation [OK]

Hint: Separate VPCs isolate teams best, avoid shared subnets [OK]

Common Mistakes:

• Relying only on firewall rules inside one VPC
• Using public IPs for internal isolation
• Connecting all resources in one VPC without restrictions