Question

Difficulty: EasyConfigure Azure Load Balancer

Your company is deploying a new public-facing application in Azure. You plan to distribute traffic to the application's virtual machines using a Standard Load Balancer. Which two configurations are compatible and supported for this Standard Load Balancer deployment?

  1. A frontend IP configuration that uses a Standard SKU public IP addressAnswer
  2. Backend pool virtual machines located in different virtual networks within the same regionAnswer
  3. C
    A frontend IP configuration that uses a Basic SKU public IP address
  4. D
    Backend pool virtual machines that have Basic SKU public IP addresses assigned to their network interfaces

Answer

The Standard Load Balancer must use a Standard SKU public IP address for its frontend configuration, and its backend pool can contain virtual machines from any virtual network within the same region.
A Standard Load Balancer requires Standard SKU public IP addresses for its frontend and any instance-level public IPs on the backend VMs. It also supports virtual machines from any virtual network in the same region as backend pool members.

Step-by-Step Solution

1
Identify the Load Balancer SKU.
The scenario specifies a Standard Load Balancer.
SKU limits dictate the compatible options for frontends and backend pools.
2
Determine the frontend IP configuration requirements.
The public IP address used for the frontend must be a Standard SKU public IP address.
Standard Load Balancers require Standard SKU public IPs; Basic SKU public IPs are incompatible.
3
Determine the backend pool membership requirements.
The backend pool can include virtual machines from any virtual network in the same region, and any instance-level public IPs on these VMs must also be Standard SKU.
Standard Load Balancers support cross-VNet backend pools, but require all IP resources to share the same SKU.

Key Concept

SKU compatibility and backend pool features of Azure Standard Load Balancer
Rate this question