Backend pools and health probes in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does a health probe affect backend pool traffic?

In Azure Load Balancer, what happens when a backend pool VM fails the health probe?

A The VM is restarted automatically by the load balancer.

B The VM continues to receive traffic but logs an error.

C The VM is removed from the backend pool and stops receiving new traffic.

D The load balancer redirects traffic to the failing VM to test recovery.

💡 Hint

Think about how the load balancer ensures only healthy VMs get traffic.

The health probe checks VM health. If a VM fails, it is removed from the backend pool to avoid sending traffic to an unhealthy VM.

❓ Configuration

intermediate

Identify the correct health probe configuration for TCP port 80

Which Azure CLI command correctly creates a TCP health probe on port 80 for a load balancer?

A az network lb probe create --resource-group MyRG --lb-name MyLB --name MyProbe --protocol Http --port 80

B az network lb probe create --resource-group MyRG --lb-name MyLB --name MyProbe --protocol Udp --port 80

C az network lb probe create --resource-group MyRG --lb-name MyLB --name MyProbe --protocol Tcp --port 443

D az network lb probe create --resource-group MyRG --lb-name MyLB --name MyProbe --protocol Tcp --port 80

💡 Hint

Check the protocol and port number carefully.

TCP protocol with port 80 is correct for a TCP health probe on port 80. HTTP protocol or other ports do not match the requirement.

❓ Architecture

advanced

Designing backend pools for high availability

You want to design an Azure Load Balancer backend pool to ensure high availability across two regions. Which approach is best?

A Create separate backend pools in each region and use Traffic Manager to route traffic.

B Add all VMs from both regions into a single backend pool on one load balancer.

C Configure backend pools only in the primary region and failover manually.

D Use a single VM in one region as the backend pool to simplify management.

💡 Hint

Consider geographic redundancy and traffic routing.

Using separate backend pools per region with Traffic Manager allows routing users to the closest healthy region, ensuring high availability.

❓ security

advanced

Securing health probes from unauthorized access

How can you secure Azure Load Balancer health probes to prevent unauthorized access to backend VMs?

A Configure Network Security Groups to allow probe IP ranges only on probe ports.

B Disable health probes and rely on manual monitoring.

C Allow all inbound traffic to backend VMs to ensure probes work.

D Use public IP addresses for backend VMs to isolate probes.

💡 Hint

Think about controlling network traffic to only trusted sources.

Network Security Groups can restrict probe traffic to only the load balancer's IP ranges and ports, securing backend VMs from unauthorized access.

✅ Best Practice

expert

Optimizing health probe intervals for backend responsiveness

What is the best practice for setting health probe interval and unhealthy threshold to quickly detect backend failures without causing false positives?

A Set a long interval (60 seconds) and a high unhealthy threshold (10) to reduce load.

B Set a short interval (5 seconds) and a low unhealthy threshold (2) for fast detection.

C Set interval and threshold to 1 to detect failures instantly.

D Disable health probes and monitor backend manually.

💡 Hint

Balance detection speed and avoiding false alarms.

A short interval with a low threshold allows quick detection of failures while avoiding false positives from transient issues.

Practice

1. What is the main purpose of a backend pool in Azure Load Balancer?

easy

A. To create virtual networks

B. To monitor the health of servers

C. To store user data securely

D. To group servers that will share incoming user requests

Solution

1. Step 1: Understand backend pool role

   A backend pool groups multiple servers to distribute incoming traffic among them.

2. Step 2: Differentiate from health probes

   Health probes check server status, but backend pools organize servers for load balancing.

3. Final Answer:

   To group servers that will share incoming user requests -> Option D

4. Quick Check:

   Backend pool = group servers for requests [OK]

Hint: Backend pools group servers; health probes check server status [OK]

Common Mistakes:

• Confusing backend pools with health probes
• Thinking backend pools store data
• Mixing backend pools with network creation

2. Which of the following is the correct way to define a health probe in Azure Load Balancer configuration?

easy

A. healthProbe: { protocol: 'TCP', port: 80, intervalInSeconds: 15, numberOfProbes: 2 }

B. healthProbe: { protocol: 'FTP', port: 21, intervalInSeconds: 10, numberOfProbes: 3 }

C. healthProbe: { protocol: 'HTTP', port: 8080, intervalInSeconds: 5, numberOfProbes: 1 }

D. healthProbe: { protocol: 'UDP', port: 53, intervalInSeconds: 20, numberOfProbes: 4 }

Solution

1. Step 1: Identify valid protocols for health probes

   Azure Load Balancer supports TCP and HTTP probes; FTP and UDP are invalid.

2. Step 2: Check probe parameters

   healthProbe: { protocol: 'TCP', port: 80, intervalInSeconds: 15, numberOfProbes: 2 } uses TCP on port 80 with reasonable intervals and probe counts, matching best practices.

3. Final Answer:

   healthProbe: { protocol: 'TCP', port: 80, intervalInSeconds: 15, numberOfProbes: 2 } -> Option A

4. Quick Check:

   Valid protocol and settings = healthProbe: { protocol: 'TCP', port: 80, intervalInSeconds: 15, numberOfProbes: 2 } [OK]

Hint: Use TCP or HTTP protocols for health probes in Azure [OK]

Common Mistakes:

• Using unsupported protocols like FTP or UDP
• Setting too few probes causing false negatives
• Choosing invalid port numbers

3. Given this health probe configuration:

protocol: 'HTTP', port: 8080, intervalInSeconds: 10, numberOfProbes: 3

If the backend server responds successfully on the first two probes but fails on the third, what will Azure Load Balancer do?

medium

A. Mark the server as unhealthy immediately after the first failure

B. Mark the server as unhealthy after three consecutive failures

C. Ignore the probe results and keep the server in the pool

D. Keep the server as healthy because two successful probes passed

Solution

1. Step 1: Understand numberOfProbes meaning

   numberOfProbes defines how many consecutive failed probes mark a server unhealthy.

2. Step 2: Analyze probe results

   Only one failure occurred, so the server is still healthy until 3 consecutive failures happen.

3. Final Answer:

   Mark the server as unhealthy after three consecutive failures -> Option B

4. Quick Check:

   3 failures needed to mark unhealthy = Mark the server as unhealthy after three consecutive failures [OK]

Hint: Server unhealthy after consecutive failed probes count reached [OK]

Common Mistakes:

• Marking unhealthy after a single failure
• Ignoring the numberOfProbes setting
• Assuming any failure removes server immediately

4. You configured a backend pool with three servers and a health probe. One server is always marked unhealthy even though it is running fine. What is the most likely cause?

medium

A. Backend pool has too many servers

B. Load balancer is not assigned a public IP

C. Health probe is configured with the wrong port or protocol

D. The backend server is overloaded with traffic

Solution

1. Step 1: Check health probe configuration

   If the probe uses the wrong port or protocol, it will fail to get a healthy response from the server.

2. Step 2: Rule out other causes

   Too many servers or missing public IP do not cause probe failures; overload affects performance but not probe success directly.

3. Final Answer:

   Health probe is configured with the wrong port or protocol -> Option C

4. Quick Check:

   Wrong probe config causes false unhealthy status [OK]

Hint: Check probe port and protocol if server shows unhealthy wrongly [OK]

Common Mistakes:

• Blaming backend pool size for probe failures
• Ignoring probe configuration details
• Assuming public IP affects probe health

5. You want to ensure high availability for your web app using Azure Load Balancer. You have three backend servers and want to configure health probes and backend pools. Which combination best improves reliability and performance?

hard

A. Create a backend pool with all three servers and a TCP health probe on port 80 with 5-second intervals and 2 probes

B. Create separate backend pools for each server and no health probes

C. Create a backend pool with two servers only and an HTTP health probe on port 8080 with 30-second intervals and 5 probes

D. Create a backend pool with all servers and a health probe using unsupported protocol FTP

Solution

1. Step 1: Use a single backend pool for load distribution

   Grouping all servers in one backend pool balances traffic and improves availability.

2. Step 2: Configure a valid health probe with appropriate settings

   TCP probe on port 80 with short intervals and few probes quickly detects unhealthy servers.

3. Step 3: Evaluate other options

   Separate pools reduce load balancing benefits; no probes risk sending traffic to bad servers; unsupported protocols cause failures.

4. Final Answer:

   Create a backend pool with all three servers and a TCP health probe on port 80 with 5-second intervals and 2 probes -> Option A

5. Quick Check:

   All servers + valid probe = best reliability [OK]

Hint: Use all servers in one pool with valid health probe for best uptime [OK]

Common Mistakes:

• Splitting servers into multiple pools unnecessarily
• Skipping health probes
• Using unsupported protocols for probes