Why load balancing matters in GCP - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a load balancer that distributes traffic evenly.

GCP

gcloud compute forwarding-rules create my-load-balancer --load-balancing-scheme=[1] --ports=80 --target-pool=my-pool

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

AEXTERNAL

BDYNAMIC

CSTATIC

DINTERNAL

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing INTERNAL when traffic is from the internet.

The load balancing scheme should be EXTERNAL to distribute traffic from the internet to backend instances.

2fill in blank

medium

Complete the code to specify the protocol used by the load balancer.

GCP

gcloud compute forwarding-rules create my-load-balancer --load-balancing-scheme=EXTERNAL --ports=[1] --target-pool=my-pool

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

A443

B80

C22

D3306

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 443 which is for HTTPS.

Port 80 is used for HTTP traffic, which is common for web load balancing.

3fill in blank

hard

Fix the error in the backend service creation command to enable health checks.

GCP

gcloud compute backend-services create my-backend --protocol=HTTP --health-checks=[1] --global

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

Amy-health-check

Bdefault-check

Chealth-check-1

Dcheck-health

Attempts:

3 left

💡 Hint

Common Mistakes

Using a health check name that does not exist.

The health check must match the name of the created health check resource, here my-health-check.

4fill in blank

hard

Fill both blanks to create a firewall rule allowing load balancer health checks.

GCP

gcloud compute firewall-rules create allow-health-checks --direction=INGRESS --priority=1000 --network=default --action=ALLOW --rules=[1] --source-ranges=[2]

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

Atcp:80

Bicmp

C130.211.0.0/22

D0.0.0.0/0

Attempts:

3 left

💡 Hint

Common Mistakes

Allowing all IPs (0.0.0.0/0) which is insecure.

Health checks use TCP port 80 and come from the IP range 130.211.0.0/22.

5fill in blank

hard

Fill the blanks to configure a backend service with session affinity and timeout.

GCP

gcloud compute backend-services create my-backend --protocol=HTTP --session-affinity=[1] --timeout-sec=[2] --health-checks=my-health-check --global

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

ACLIENT_IP

B30

C60

DNONE

Attempts:

3 left

💡 Hint

Common Mistakes

Using too high timeout causing delays.

Session affinity is set to CLIENT_IP to keep user sessions consistent, timeout is 30 seconds.