Load balancer types comparison in GCP - Mini Project: Build & Apply

Load Balancer Types Comparison in GCP

📖 Scenario: You are working as a cloud engineer for a company that wants to understand different types of load balancers available in Google Cloud Platform (GCP). They want a simple programmatic way to compare the main types of load balancers by their key features.

🎯 Goal: Create a Python dictionary that holds the main GCP load balancer types as keys and their key features as values. Then add a configuration variable to select a load balancer type. Next, write code to extract the features of the selected load balancer. Finally, complete the code by adding a summary dictionary entry for all load balancers.

📋 What You'll Learn

Create a dictionary called load_balancers with these exact keys: 'HTTP(S) Load Balancer', 'TCP Proxy Load Balancer', 'SSL Proxy Load Balancer', 'Network Load Balancer'

Each key must map to a list of exactly these features (strings):

- HTTP(S) Load Balancer: 'Global', 'Layer 7', 'Supports HTTP and HTTPS'

- TCP Proxy Load Balancer: 'Global', 'Layer 4', 'TCP traffic only'

- SSL Proxy Load Balancer: 'Global', 'Layer 4', 'SSL traffic only'

- Network Load Balancer: 'Regional', 'Layer 4', 'TCP and UDP traffic'

Create a variable called selected_lb and set it to the string 'HTTP(S) Load Balancer'

Write code to get the features list for the selected_lb from load_balancers and store it in a variable called features

Add a new dictionary entry to load_balancers with key 'Summary' and value as a list of all load balancer keys except 'Summary'

💡 Why This Matters

🌍 Real World

Cloud engineers often need to compare and document different cloud services to choose the right one for their applications.

💼 Career

Understanding load balancer types and their features is essential for designing scalable and reliable cloud architectures.

1

Create the load balancers dictionary

Create a dictionary called load_balancers with these exact keys and values: 'HTTP(S) Load Balancer' mapped to ['Global', 'Layer 7', 'Supports HTTP and HTTPS'], 'TCP Proxy Load Balancer' mapped to ['Global', 'Layer 4', 'TCP traffic only'], 'SSL Proxy Load Balancer' mapped to ['Global', 'Layer 4', 'SSL traffic only'], and 'Network Load Balancer' mapped to ['Regional', 'Layer 4', 'TCP and UDP traffic'].

GCP

# Create the load_balancers dictionary with the specified keys and values
# Your code here

Hint

Use a Python dictionary with the exact keys and list values as specified.

2

Add selected load balancer variable

Create a variable called selected_lb and set it to the string 'HTTP(S) Load Balancer'.

GCP

load_balancers = {
    'HTTP(S) Load Balancer': ['Global', 'Layer 7', 'Supports HTTP and HTTPS'],
    'TCP Proxy Load Balancer': ['Global', 'Layer 4', 'TCP traffic only'],
    'SSL Proxy Load Balancer': ['Global', 'Layer 4', 'SSL traffic only'],
    'Network Load Balancer': ['Regional', 'Layer 4', 'TCP and UDP traffic']
}
# Create the selected_lb variable and set it to 'HTTP(S) Load Balancer'
# Your code here

Hint

Assign the exact string to the variable selected_lb.

3

Extract features of selected load balancer

Write code to get the features list for the load balancer stored in selected_lb from the load_balancers dictionary and store it in a variable called features.

GCP

load_balancers = {
    'HTTP(S) Load Balancer': ['Global', 'Layer 7', 'Supports HTTP and HTTPS'],
    'TCP Proxy Load Balancer': ['Global', 'Layer 4', 'TCP traffic only'],
    'SSL Proxy Load Balancer': ['Global', 'Layer 4', 'SSL traffic only'],
    'Network Load Balancer': ['Regional', 'Layer 4', 'TCP and UDP traffic']
}
selected_lb = 'HTTP(S) Load Balancer'
# Get the features list for selected_lb and store in features
# Your code here

Hint

Use dictionary access with the variable selected_lb as the key.

4

Add summary entry to load balancers dictionary

Add a new dictionary entry to load_balancers with the key 'Summary' and the value as a list of all load balancer keys except 'Summary' itself.

GCP

load_balancers = {
    'HTTP(S) Load Balancer': ['Global', 'Layer 7', 'Supports HTTP and HTTPS'],
    'TCP Proxy Load Balancer': ['Global', 'Layer 4', 'TCP traffic only'],
    'SSL Proxy Load Balancer': ['Global', 'Layer 4', 'SSL traffic only'],
    'Network Load Balancer': ['Regional', 'Layer 4', 'TCP and UDP traffic']
}
selected_lb = 'HTTP(S) Load Balancer'
features = load_balancers[selected_lb]
# Add a 'Summary' key to load_balancers with a list of all load balancer keys except 'Summary'
# Your code here

Hint

Use a list comprehension to get all keys except 'Summary' and assign it to load_balancers['Summary'].

Practice

1. Which GCP load balancer type is best suited for distributing HTTP and HTTPS traffic globally with SSL termination?

easy

A. TCP Proxy Load Balancer

B. Internal Load Balancer

C. Network Load Balancer

D. HTTP(S) Load Balancer

Solution

1. Step 1: Understand the traffic type

   HTTP and HTTPS traffic require Layer 7 (application layer) handling with SSL termination.

2. Step 2: Match load balancer capabilities

   HTTP(S) Load Balancer supports global distribution and SSL termination for web traffic.

3. Final Answer:

   HTTP(S) Load Balancer -> Option D

4. Quick Check:

   HTTP/HTTPS + SSL termination = HTTP(S) Load Balancer [OK]

Hint: Web traffic with SSL? Pick HTTP(S) Load Balancer [OK]

Common Mistakes:

• Confusing TCP Proxy with HTTP(S) for web traffic
• Choosing Network Load Balancer for HTTPS termination
• Using Internal Load Balancer for global traffic

2. Which GCP load balancer type uses a regional forwarding rule and supports TCP and UDP traffic without SSL termination?

easy

A. HTTP(S) Load Balancer

B. Network Load Balancer

C. TCP Proxy Load Balancer

D. Internal Load Balancer

Solution

1. Step 1: Identify the traffic and forwarding rule type

   TCP and UDP traffic with regional forwarding rules indicates a Layer 4 load balancer.

2. Step 2: Match with GCP load balancer types

   Network Load Balancer supports TCP/UDP traffic regionally without SSL termination.

3. Final Answer:

   Network Load Balancer -> Option B

4. Quick Check:

   TCP/UDP + regional + no SSL = Network Load Balancer [OK]

Hint: TCP/UDP regional traffic? Use Network Load Balancer [OK]

Common Mistakes:

• Choosing HTTP(S) Load Balancer for UDP traffic
• Confusing TCP Proxy with Network Load Balancer
• Selecting Internal Load Balancer for external traffic

3. Given this scenario: You want to load balance TCP traffic globally with SSL offloading. Which GCP load balancer type will you use?

client -> GCP LB -> backend instances (TCP with SSL offloading)

medium

A. TCP Proxy Load Balancer

B. Internal Load Balancer

C. Network Load Balancer

D. HTTP(S) Load Balancer

Solution

1. Step 1: Analyze traffic and SSL offloading need

   TCP traffic with SSL offloading requires Layer 4 proxy with SSL termination.

2. Step 2: Match with GCP load balancer types

   TCP Proxy Load Balancer supports global TCP traffic with SSL offloading.

3. Final Answer:

   TCP Proxy Load Balancer -> Option A

4. Quick Check:

   Global TCP + SSL offloading = TCP Proxy Load Balancer [OK]

Hint: Global TCP + SSL offload? Use TCP Proxy Load Balancer [OK]

Common Mistakes:

• Choosing Network Load Balancer which lacks SSL offloading
• Selecting HTTP(S) Load Balancer for TCP traffic
• Using Internal Load Balancer for external traffic

4. You configured an Internal Load Balancer but your clients outside the VPC cannot access the service. What is the most likely cause?

medium

A. Internal Load Balancer only supports traffic inside the VPC

B. You forgot to enable global forwarding rules

C. Internal Load Balancer does not support TCP traffic

D. You need to use HTTP(S) Load Balancer for internal traffic

Solution

1. Step 1: Understand Internal Load Balancer scope

   Internal Load Balancer is designed for traffic inside a VPC or connected networks only.

2. Step 2: Identify access limitation

   Clients outside the VPC cannot reach Internal Load Balancer because it does not expose external IPs.

3. Final Answer:

   Internal Load Balancer only supports traffic inside the VPC -> Option A

4. Quick Check:

   Internal LB = VPC-only traffic [OK]

Hint: Internal LB is VPC-only; external clients can't connect [OK]

Common Mistakes:

• Assuming Internal LB supports global forwarding
• Thinking Internal LB supports external TCP traffic
• Confusing Internal LB with HTTP(S) Load Balancer

5. You have a multi-region web app serving HTTP and HTTPS traffic with backend services in multiple zones. You want to minimize latency and provide automatic failover. Which GCP load balancer type should you choose and why?

hard

A. Network Load Balancer because it supports UDP and TCP globally

B. Internal Load Balancer because it routes traffic inside the VPC

C. HTTP(S) Load Balancer because it offers global load balancing with SSL termination and health checks

D. TCP Proxy Load Balancer because it handles TCP traffic with SSL offloading

Solution

1. Step 1: Analyze requirements for multi-region HTTP/HTTPS app

   Needs global load balancing, SSL termination, low latency, and failover.

2. Step 2: Match load balancer features

   HTTP(S) Load Balancer supports global distribution, SSL termination, health checks, and automatic failover.

3. Step 3: Exclude other options

   Network Load Balancer is regional and lacks SSL termination; Internal Load Balancer is internal-only; TCP Proxy is for TCP, not HTTP/HTTPS.

4. Final Answer:

   HTTP(S) Load Balancer because it offers global load balancing with SSL termination and health checks -> Option C

5. Quick Check:

   Multi-region HTTP/HTTPS + failover = HTTP(S) Load Balancer [OK]

Hint: Global web app? Pick HTTP(S) Load Balancer for SSL and failover [OK]

Common Mistakes:

• Choosing Network Load Balancer for HTTP/HTTPS global traffic
• Using Internal Load Balancer for external multi-region access
• Selecting TCP Proxy Load Balancer for HTTP traffic