Question

Difficulty: EasyConfigure Azure Load Balancer

You are configuring a public Azure Load Balancer. You have provisioned a public IP address named IP-Front that uses the Basic SKU. You plan to distribute traffic to virtual machines.

Which two configurations must you select to ensure compatibility with IP-Front?

  1. A Basic SKU Load BalancerAnswer
  2. Virtual machines deployed within a single Availability SetAnswer
  3. C
    A Standard SKU Load Balancer
  4. D
    Virtual machines deployed across multiple Availability Zones
  5. E
    Virtual machines deployed in different Virtual Networks

Answer

To ensure compatibility with a Basic SKU public IP address, you must configure a Basic SKU Load Balancer and ensure the backend virtual machines are deployed within a single Availability Set.
The correct options are a Basic SKU Load Balancer and virtual machines deployed within a single Availability Set. Azure requires the Load Balancer SKU to match the Public IP SKU. A Basic SKU Public IP can only be associated with a Basic SKU Load Balancer. Additionally, the backend pool of a Basic SKU Load Balancer is restricted to virtual machines that reside within the same Availability Set or Virtual Machine Scale Set.

Step-by-Step Solution

1
Identify the IP address SKU and its compatibility constraints.
The public IP address uses the Basic SKU. Azure requires that the public IP address SKU matches the Load Balancer SKU. Therefore, a Basic SKU Load Balancer must be selected.
Standard Load Balancers require Standard Public IPs, while Basic Load Balancers require Basic Public IPs.
2
Determine the backend pool configuration constraints for the selected Load Balancer SKU.
The Basic SKU Load Balancer limits the backend pool to virtual machines residing in a single Availability Set or Virtual Machine Scale Set.
Basic Load Balancers do not support cross-availability zone or cross-virtual network backend pools, which are capabilities reserved for the Standard SKU Load Balancer.

Key Concept

Azure Load Balancer SKU selection and backend pool constraints
Rate this question