Why advanced networking matters in GCP - Why It Works

Introduction

Advanced networking helps connect different parts of your cloud setup securely and quickly. It solves problems like slow connections, security risks, and managing many devices or services talking to each other.

When you want to connect multiple cloud services securely without exposing them to the public internet

When your app needs to handle lots of users and data without slowing down

When you want to control who can access your cloud resources and how

When you need to connect your cloud setup to your office network safely

When you want to monitor and manage traffic between your cloud services

Commands

This command creates a new custom network in Google Cloud where you can define your own subnets for better control.

Terminal

gcloud compute networks create example-network --subnet-mode=custom

Expected Output

Created [https://www.googleapis.com/compute/v1/projects/example-project/global/networks/example-network].

→

--subnet-mode=custom - Allows you to create and manage your own subnets instead of using automatic ones.

This command creates a subnet within your custom network to organize your resources in a specific region with a defined IP range.

Terminal

gcloud compute networks subnets create example-subnet --network=example-network --region=us-central1 --range=10.0.0.0/24

Expected Output

Created [https://www.googleapis.com/compute/v1/projects/example-project/regions/us-central1/subnetworks/example-subnet].

→

--region=us-central1 - Specifies the region where the subnet will be created.

→

--range=10.0.0.0/24 - Defines the IP address range for the subnet.

This command creates a firewall rule to allow internal communication between resources in the subnet using common protocols.

Terminal

gcloud compute firewall-rules create allow-internal --network=example-network --allow tcp,udp,icmp --source-ranges=10.0.0.0/24

Expected Output

Created [https://www.googleapis.com/compute/v1/projects/example-project/global/firewalls/allow-internal].

→

--allow tcp,udp,icmp - Allows traffic for TCP, UDP, and ICMP protocols.

→

--source-ranges=10.0.0.0/24 - Limits the rule to traffic coming from the subnet's IP range.

This command lists all firewall rules applied to your custom network so you can verify your security settings.

Terminal

gcloud compute firewall-rules list --filter='network=example-network'

Expected Output

NAME           NETWORK          DIRECTION  PRIORITY  ALLOW           DENY  DISABLED

allow-internal example-network  INGRESS    1000      tcp,udp,icmp          False

→

--filter='network=example-network' - Filters the list to show only rules for the specified network.

Key Concept

If you remember nothing else from this pattern, remember: advanced networking lets you control how your cloud resources connect and stay safe.

Common Mistakes

Using automatic subnet mode instead of custom when you need precise control

Automatic mode creates subnets you cannot customize, limiting your network design.

Always use --subnet-mode=custom when you want to define your own subnets.

Not setting firewall rules to allow internal traffic

Resources in the network cannot communicate, causing app failures.

Create firewall rules that allow necessary protocols within your subnet IP range.

Forgetting to specify the region when creating subnets

The command fails or creates resources in unintended locations.

Always include the --region flag with the correct region.

Summary

Create a custom network to control your cloud connections.

Add subnets with specific IP ranges in chosen regions.

Set firewall rules to allow safe communication inside your network.

Verify your firewall rules to ensure proper security.

Practice

1. Why is advanced networking important in Google Cloud Platform (GCP)?

easy

A. It helps connect cloud resources securely and efficiently.

B. It automatically fixes all software bugs.

C. It increases the size of virtual machines.

D. It reduces the cost of cloud storage.

Solution

1. Step 1: Understand the role of networking in cloud

   Networking connects different cloud resources so they can communicate.

2. Step 2: Recognize the benefits of advanced networking

   Advanced networking adds security and efficiency to these connections.

3. Final Answer:

   It helps connect cloud resources securely and efficiently. -> Option A

4. Quick Check:

   Advanced networking = secure, efficient connections [OK]

Hint: Think about how cloud parts talk safely and fast [OK]

Common Mistakes:

• Confusing networking with software debugging
• Mixing networking with storage or VM sizing
• Assuming networking reduces costs directly

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

easy

A. gcloud compute networks new my-network --subnet-mode=auto

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

C. gcloud network create my-network --subnet=custom

D. gcloud compute create network my-network --mode=auto

Solution

1. Step 1: Recall gcloud command syntax for creating networks

   The correct command uses 'gcloud compute networks create' with '--subnet-mode=custom' to specify custom subnets.

2. Step 2: Check each option for correct syntax

   gcloud compute networks create my-network --subnet-mode=custom matches the correct syntax; others have wrong commands or flags.

3. Final Answer:

   gcloud compute networks create my-network --subnet-mode=custom -> Option B

4. Quick Check:

   Correct gcloud network create syntax = gcloud compute networks create my-network --subnet-mode=custom [OK]

Hint: Remember 'gcloud compute networks create' plus subnet mode [OK]

Common Mistakes:

• Using 'create network' instead of 'networks create'
• Mixing 'subnet-mode' with wrong flags
• Using 'new' instead of 'create'

3. Given this firewall rule configuration in GCP, what will happen if you try to connect to a VM on port 22 (SSH)?

gcloud compute firewall-rules create allow-ssh --network=my-network --allow=tcp:22 --source-ranges=10.0.0.0/24

medium

A. SSH connections from IPs outside 10.0.0.0/24 will be blocked.

B. SSH connections from any IP address will be allowed.

C. All traffic to port 22 will be blocked.

D. SSH connections from 0.0.0.0/0 will be allowed.

Solution

1. Step 1: Analyze the firewall rule source range

   The rule allows TCP port 22 only from IPs in 10.0.0.0/24 subnet.

2. Step 2: Understand effect on SSH connections

   SSH from IPs outside 10.0.0.0/24 will be blocked because no rule allows them.

3. Final Answer:

   SSH connections from IPs outside 10.0.0.0/24 will be blocked. -> Option A

4. Quick Check:

   Firewall source range limits access = SSH connections from IPs outside 10.0.0.0/24 will be blocked. [OK]

Hint: Check source-ranges to see who can connect [OK]

Common Mistakes:

• Assuming all IPs can connect
• Confusing source-ranges with destination
• Ignoring firewall rule specificity

4. You created a custom subnet in GCP but your VM instances cannot reach the internet. What is the most likely cause?

medium

A. The VM instances have static internal IPs.

B. Firewall rules allow all outbound traffic.

C. The subnet is set to auto mode.

D. No Cloud NAT or external IP assigned to the VM instances.

Solution

1. Step 1: Understand internet access requirements

   VMs in custom subnets need either external IPs or Cloud NAT to access the internet.

2. Step 2: Identify missing component

   If VMs lack external IPs and no Cloud NAT is configured, they cannot reach the internet.

3. Final Answer:

   No Cloud NAT or external IP assigned to the VM instances. -> Option D

4. Quick Check:

   Internet access needs NAT or external IP [OK]

Hint: Check if VMs have external IP or Cloud NAT [OK]

Common Mistakes:

• Assuming firewall rules block outbound by default
• Confusing auto and custom subnet modes
• Thinking static internal IPs block internet

5. You want to design a GCP network architecture that isolates sensitive workloads but allows secure communication between them and public-facing services. Which advanced networking features should you combine?

hard

A. Assign public IPs to all VMs and disable firewall rules.

B. Use a single auto mode VPC with no firewall rules.

C. Use separate custom VPCs with VPC peering and firewall rules to control traffic.

D. Use default network and rely on default firewall rules.

Solution

1. Step 1: Identify isolation and secure communication needs

   Separate VPCs isolate workloads; VPC peering allows controlled communication.

2. Step 2: Apply firewall rules for traffic control

   Firewall rules restrict and allow only needed traffic between workloads and public services.

3. Final Answer:

   Use separate custom VPCs with VPC peering and firewall rules to control traffic. -> Option C

4. Quick Check:

   Isolation + secure communication = VPC peering + firewall [OK]

Hint: Combine VPC peering and firewall rules for isolation and access [OK]

Common Mistakes:

• Using auto mode VPCs without control
• Assigning public IPs to sensitive workloads
• Relying on default network without customization