Load balancing rules in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the protocol for the load balancing rule.

Azure

load_balancer_rule = {
  "name": "myLoadBalancingRule",
  "protocol": "[1]",
  "frontendPort": 80,
  "backendPort": 80
}

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

AUDP

BTCP

CHTTP

DFTP

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing UDP when the service requires reliable connection.

Using application protocols like HTTP instead of transport protocols.

The protocol for load balancing rules is typically set to TCP or UDP. Here, TCP is the correct choice for HTTP traffic.

2fill in blank

medium

Complete the code to set the frontend port for the load balancing rule.

Azure

load_balancer_rule = {
  "name": "myLoadBalancingRule",
  "protocol": "TCP",
  "frontendPort": [1],
  "backendPort": 80
}

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

A22

B8080

C443

D80

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 22 which is for SSH.

Confusing frontend and backend ports.

The frontend port is the port on which the load balancer listens. Port 80 is standard for HTTP traffic.

3fill in blank

hard

Fix the error in the load balancing rule by completing the backend port correctly.

Azure

load_balancer_rule = {
  "name": "myLoadBalancingRule",
  "protocol": "TCP",
  "frontendPort": 80,
  "backendPort": [1]
}

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

A22

B443

C80

D21

Attempts:

3 left

💡 Hint

Common Mistakes

Setting backend port to SSH or FTP ports.

Mismatching frontend and backend ports.

The backend port should match the port on which the backend servers listen. For HTTP, this is usually port 80.

4fill in blank

hard

Fill both blanks to configure the load balancing rule with the correct frontend IP configuration and idle timeout.

Azure

load_balancer_rule = {
  "name": "myLoadBalancingRule",
  "frontendIPConfiguration": [1],
  "idleTimeoutInMinutes": [2]
}

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

A"frontendIPConfig1"

B"backendIPConfig1"

C4

D30

Attempts:

3 left

💡 Hint

Common Mistakes

Using backend IP config for frontend IP configuration.

Setting idle timeout too low causing premature disconnections.

The frontend IP configuration must reference the frontend IP, here "frontendIPConfig1". The idle timeout is commonly set to 30 minutes to keep connections alive.

5fill in blank

hard

Fill all three blanks to complete the load balancing rule with correct protocol, load distribution, and enable floating IP.

Azure

load_balancer_rule = {
  "name": "myLoadBalancingRule",
  "protocol": "[1]",
  "loadDistribution": "[2]",
  "enableFloatingIP": [3]
}

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

ATCP

BSourceIP

Ctrue

DUDP

Attempts:

3 left

💡 Hint

Common Mistakes

Using UDP when TCP is required.

Disabling floating IP when needed for certain scenarios.

The protocol is set to TCP for reliable connections. Load distribution by SourceIP ensures requests from the same client go to the same backend. Floating IP enabled (true) allows direct server return traffic.