Examkin

Question

Difficulty: Very hardConfigure Azure Load Balancer

An administrator is configuring load balancing for a web application in an Azure subscription. The environment contains the following resources:
- A virtual network named VNet1 that has a single subnet named Subnet1.
- A virtual machine named VM1 deployed in Availability Zone 1. VM1 has a network interface named NIC1 connected to Subnet1. NIC1 has a Basic SKU public IP address named VM1-PIP assigned to its IP configuration.
- A virtual machine named VM2 deployed in Availability Zone 1. VM2 has a network interface named NIC2 connected to Subnet1 with no public IP address.
- A virtual machine named VM3 deployed in Availability Zone 2. VM3 has a network interface named NIC3 connected to Subnet1 with no public IP address.

You deploy a public Azure Load Balancer named LB1 using the Standard SKU. You associate LB1 with a Standard SKU public IP address named LB-PIP.

When you attempt to add VM1, VM2, and VM3 to the backend pool of LB1, the configuration fails with a SKU mismatch error.

Which action should you perform to successfully add all three virtual machines to the backend pool of LB1?

  1. A
    Recreate the load balancer as a Basic SKU load balancer and configure its frontend to use a Basic SKU public IP address.
  2. B
    Place VM1, VM2, and VM3 into a new Availability Set and associate the Availability Set with the Standard load balancer's backend pool.
  3. C
    Create a new subnet in VNet1, move VM3 to the new subnet, and then associate the subnet with the backend pool of the load balancer.
  4. Dissociate the Basic SKU public IP address from the network interface of VM1, or upgrade it to a Standard SKU public IP address.Answer

Answer

Dissociate the Basic SKU public IP address from the network interface of VM1, or upgrade it to a Standard SKU public IP address.
The correct action is to dissociate the Basic SKU public IP address from the network interface of the virtual machine or upgrade it to a Standard SKU public IP address. Azure Standard Load Balancer backend pool members cannot have any Basic SKU public IPs associated with their network interfaces. All public IP addresses on network interfaces in the backend pool of a Standard Load Balancer must be of the Standard SKU.

Step-by-Step Solution

1
Identify the SKU of the load balancer and its backend pool requirements.
The Standard SKU load balancer is deployed, which requires all backend network interfaces to use Standard SKU resources (or no public IP) and supports cross-zone backend configurations.
Understanding Standard SKU requirements is necessary to locate the source of the deployment failure.
2
Analyze the IP configurations of the virtual machines in the backend pool.
VM1 has a Basic SKU public IP (VM1-PIP) assigned to its NIC, whereas VM2 and VM3 do not have public IPs.
A Basic SKU public IP directly assigned to a network interface in a Standard Load Balancer's backend pool causes a SKU mismatch error.
3
Determine the resolution for the SKU mismatch.
Dissociate VM1-PIP from VM1's NIC or upgrade VM1-PIP to the Standard SKU.
Eliminating the Basic SKU dependency on the network interface enables the VM to be successfully added to the Standard Load Balancer backend pool.

Key Concept

Standard Load Balancer backend pool member SKU compatibility constraints
Estimated Time:3m 0s
Rate this question

Topics

Configure Azure Load Balancer

More questions from this topic