TCP/UDP Load Balancer (Layer 4) in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the protocol for the load balancer.

GCP

load_balancer_config = {
  "protocol": "[1]",
  "port": 80
}

Drag options to blanks, or click blank then click option'

ATCP

BHTTP

CHTTPS

DFTP

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing HTTP or HTTPS instead of TCP

Confusing Layer 4 with Layer 7 protocols

The TCP/UDP Load Balancer operates at Layer 4, so the protocol must be set to "TCP" or "UDP". Here, "TCP" is correct.

2fill in blank

medium

Complete the code to define the backend service type for TCP/UDP load balancing.

GCP

backend_service = {
  "type": "[1]",
  "health_check": "tcp_health_check"
}

Drag options to blanks, or click blank then click option'

AHTTPS

BHTTP

CSSL

DTCP

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTP or HTTPS as backend service type

Mixing SSL with TCP backend service type

The backend service type for a TCP/UDP load balancer should be "TCP" to match the protocol and ensure proper routing.

3fill in blank

hard

Fix the error in the health check configuration for TCP load balancer.

GCP

health_check = {
  "type": "[1]",
  "port": 443
}

Drag options to blanks, or click blank then click option'

AHTTP

BHTTPS

CTCP

DSSL

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTP or HTTPS health check for TCP load balancer

Setting incorrect port for health check

For TCP load balancers, the health check type must be "TCP" to properly check backend health at Layer 4.

4fill in blank

hard

Fill both blanks to configure the forwarding rule for a TCP load balancer.

GCP

forwarding_rule = {
  "loadBalancingScheme": "[1]",
  "portRange": "[2]"
}

Drag options to blanks, or click blank then click option'

AEXTERNAL

BINTERNAL

C80-80

D443-443

Attempts:

3 left

💡 Hint

Common Mistakes

Using INTERNAL scheme for public load balancer

Setting wrong port range that doesn't match backend service

The forwarding rule for a TCP load balancer typically uses an EXTERNAL scheme and a port range like "80-80" for HTTP traffic.

5fill in blank

hard

Fill all three blanks to define the backend instance group and balancing mode.

GCP

backend = {
  "group": "[1]",
  "balancingMode": "[2]",
  "capacityScaler": [3]
}

Drag options to blanks, or click blank then click option'

A"projects/my-project/zones/us-central1-a/instanceGroups/my-group"

B"UTILIZATION"

C1.0

D"RATE"

Attempts:

3 left

💡 Hint

Common Mistakes

Using short or incorrect instance group path

Choosing RATE balancing mode when UTILIZATION is expected

Setting capacityScaler to invalid values

The backend group must specify the full instance group path. The balancing mode "UTILIZATION" balances based on resource use, and capacityScaler 1.0 means full capacity.