Question

Difficulty: EasyConfigure Azure Load Balancer

An administrator is configuring a public Azure Load Balancer to distribute internet traffic to three standalone virtual machines deployed in the same virtual network. The virtual machines are not configured within an Availability Set. The administrator deploys a Basic SKU Load Balancer, but is unable to add the virtual machines to the backend pool. Which action should the administrator take to resolve this issue?

  1. Recreate the load balancer as a Standard SKU load balancer.Answer
  2. B
    Create a Network Security Group (NSG) and associate it with each virtual machine network interface.
  3. C
    Configure a dynamic public IP address for the Basic load balancer frontend configuration.
  4. D
    Modify the load balancer distribution mode to Source IP affinity.

Answer

Recreate the load balancer as a Standard SKU load balancer.
Recreating the load balancer as a Standard SKU load balancer is the correct solution because the Standard SKU supports any virtual machine in a virtual network as a backend pool member, whereas the Basic SKU requires backend virtual machines to be within the same Availability Set or Virtual Machine Scale Set.

Step-by-Step Solution

1
Analyze the backend pool requirements for a Basic SKU load balancer.
Basic SKU load balancers restrict backend pool members to virtual machines that reside in the same Availability Set or Virtual Machine Scale Set.
To determine why the standalone virtual machines cannot be added to the backend pool.
2
Compare Basic SKU limitations with Standard SKU features.
Standard SKU load balancers support adding any virtual machine within a single virtual network to the backend pool, without requiring an Availability Set.
To identify the correct SKU that supports standalone virtual machines.
3
Select the option that matches the required SKU upgrade.
Recreating the load balancer as a Standard SKU load balancer resolves the issue.
To align the load balancer configuration with the virtual machine deployment architecture.

Key Concept

Azure Load Balancer SKU capabilities and backend pool constraints
Estimated Time:1m 0s
Rate this question