VPC peering in GCP - Time & Space Complexity

Time Complexity: VPC peering

O(n²)

Understanding Time Complexity

When connecting two private networks in the cloud, it is important to understand how the time to establish and maintain these connections grows as the number of networks increases.

We want to know how the work involved changes when more networks are linked together using VPC peering.

Scenario Under Consideration

Analyze the time complexity of creating VPC peering connections between multiple networks.

// Example: Creating VPC peering connections
for each VPC in list_of_vpcs:
  for each other_vpc in list_of_vpcs:
    if VPC != other_vpc:
      create_peering_connection(VPC, other_vpc)
      accept_peering_connection(other_vpc, VPC)

This sequence creates peering connections between every pair of VPC networks in the list.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: API calls to create and accept peering connections between pairs of VPCs.
• How many times: For each pair of distinct VPCs, two API calls are made (one to create, one to accept).

How Execution Grows With Input

As the number of VPCs increases, the number of peering connections grows quickly because each VPC connects to every other VPC.

Input Size (n)	Approx. API Calls/Operations
10	180 (each of 10 VPCs peers with 9 others, 2 calls each)
100	19,800
1000	1,998,000

Pattern observation: The number of operations grows roughly with the square of the number of VPCs, because each VPC connects to all others.

Final Time Complexity

Time Complexity: O(n²)

This means that if you double the number of VPCs, the work to create all peering connections roughly quadruples.

Common Mistake

[X] Wrong: "Adding more VPCs only increases peering work a little bit because each VPC only connects once."

[OK] Correct: Each VPC must connect to every other VPC, so the total number of connections grows much faster than the number of VPCs.

Interview Connect

Understanding how connection work grows helps you design cloud networks that scale well and avoid unexpected delays.

Self-Check

"What if we only connect each VPC to a fixed number of other VPCs instead of all? How would the time complexity change?"

Practice

1.

What is the main purpose of VPC peering in Google Cloud?

easy

A. To create a firewall rule between two networks

B. To connect two private networks securely without using the internet

C. To provide public internet access to virtual machines

D. To enable automatic backups of virtual machines

Solution

1. Step 1: Understand VPC peering concept

   VPC peering connects two private networks directly, avoiding the public internet.

2. Step 2: Compare options with concept

   Only To connect two private networks securely without using the internet describes secure private network connection without internet.

3. Final Answer:

   To connect two private networks securely without using the internet -> Option B

4. Quick Check:

   VPC peering = secure private network connection [OK]

Hint: VPC peering = private network connection, no internet needed [OK]

Common Mistakes:

• Confusing VPC peering with firewall rules
• Thinking VPC peering provides internet access
• Assuming VPC peering is for backups

2.

Which of the following is the correct command to create a VPC peering connection from net-a to net-b in Google Cloud CLI?

gcloud compute networks peerings create PEERING_NAME --network=NETWORK --peer-network=PEER_NETWORK

easy

A. gcloud compute networks peerings create peer-ab --network=net-a --peer-network=net-b

B. gcloud compute networks peerings create net-a --network=peer-ab --peer-network=net-b

C. gcloud compute networks peerings create net-b --network=net-a --peer-network=net-b

D. gcloud compute networks peerings create peer-ab --peer-network=net-a --network=net-b

Solution

1. Step 1: Identify correct command syntax

   The command requires a peering name, the local network, and the peer network.

2. Step 2: Match parameters to networks

   gcloud compute networks peerings create peer-ab --network=net-a --peer-network=net-b correctly uses a peering name and assigns net-a as local network and net-b as peer network.

3. Final Answer:

   gcloud compute networks peerings create peer-ab --network=net-a --peer-network=net-b -> Option A

4. Quick Check:

   Correct CLI syntax = gcloud compute networks peerings create peer-ab --network=net-a --peer-network=net-b [OK]

Hint: Peering name first, then --network local, --peer-network remote [OK]

Common Mistakes:

• Swapping --network and --peer-network values
• Using network names as peering name
• Omitting required flags

3.

Given two VPC networks net-a and net-b peered together, which of the following statements about routing is true?

1. Each network must create routes to the other's IP ranges.
2. Routes are automatically shared by default.
3. Peering allows communication only if firewall rules permit.
4. Peering replaces the need for VPN connections.

medium

A. Only statement 2 and 3 are true

B. Only statement 1 and 3 are true

C. Only statement 1 and 2 are true

D. Only statement 3 and 4 are true

Solution

1. Step 1: Analyze routing and firewall requirements

   VPC peering automatically shares subnet routes by default. Firewall rules still control traffic.

2. Step 2: Evaluate statements

   Statement 1 is false (no manual route creation needed). Statements 2 and 3 are true. Statement 4 is not accurate (peering and VPN serve different purposes).

3. Final Answer:

   Only statement 2 and 3 are true -> Option A

4. Quick Check:

   Routes auto + firewall needed [OK]

Hint: Routes automatically shared; firewall rules still apply [OK]

Common Mistakes:

• Thinking routes must be manually created
• Ignoring firewall rules in peering
• Thinking peering always replaces VPN

4.

You created a VPC peering between net-a and net-b, but instances in net-a cannot reach instances in net-b. What is the most likely cause?

medium

A. The peering connection was created only on net-a side

B. The peering connection was created with the wrong peering name

C. The VPC networks have overlapping IP ranges

D. Firewall rules in net-b block incoming traffic from net-a

Solution

1. Step 1: Check common connectivity issues in VPC peering

   Firewall rules must allow traffic between peered networks; blocking rules prevent communication.

2. Step 2: Evaluate other options

   Wrong peering name or one-sided peering would prevent peering creation. Overlapping IP ranges prevent peering setup itself.

3. Final Answer:

   Firewall rules in net-b block incoming traffic from net-a -> Option D

4. Quick Check:

   Firewall blocking = connectivity failure [OK]

Hint: Check firewall rules first when peering connectivity fails [OK]

Common Mistakes:

• Ignoring firewall rules as cause
• Assuming peering auto-fixes IP conflicts
• Thinking peering is one-sided

5.

You have two VPC networks, net-a with CIDR 10.0.0.0/16 and net-b with CIDR 10.0.0.0/16. You want to peer them to share resources privately. What is the best approach?

hard

A. Create VPC peering directly between net-a and net-b despite overlapping CIDRs

B. Use VPN instead of VPC peering to connect the networks

C. Change one network's CIDR to a non-overlapping range before peering

D. Use shared VPC instead of peering for overlapping CIDRs

Solution

1. Step 1: Understand CIDR overlap restrictions in VPC peering

   VPC peering requires non-overlapping IP ranges to route traffic correctly.

2. Step 2: Choose solution for overlapping CIDRs

   Changing one network's CIDR to a non-overlapping range allows peering. VPN or shared VPC are alternatives but not direct peering solutions.

3. Final Answer:

   Change one network's CIDR to a non-overlapping range before peering -> Option C

4. Quick Check:

   Non-overlapping CIDRs required for peering [OK]

Hint: Peering needs unique IP ranges; change CIDR if overlapping [OK]

Common Mistakes:

• Trying to peer overlapping CIDRs directly
• Confusing VPN with peering
• Ignoring shared VPC as different concept