Examkin

Question

Difficulty: EasyConfigure Azure Load Balancer

You plan to deploy a Standard Load Balancer in an Azure subscription. You create a public IP address to be used as the frontend for the load balancer. However, when you attempt to associate the public IP address with the Standard Load Balancer, the public IP address is not available for selection in the Azure portal. What is the most likely cause of this issue?

  1. The public IP address was created using the Basic SKU.Answer
  2. B
    The public IP address was created in a different resource group than the load balancer.
  3. C
    The public IP address is configured with dynamic IP address allocation.
  4. D
    The public IP address has not been associated with a virtual network subnet.

Answer

The public IP address was created using the Basic SKU.
An Azure Standard Load Balancer requires a Standard SKU Public IP address. Basic SKU Public IP addresses are incompatible and will not appear in the selection menu when configuring a Standard Load Balancer frontend.

Step-by-Step Solution

1
Identify the SKU requirements for the Azure Load Balancer being deployed.
The scenario specifies a Standard Load Balancer.
Standard Load Balancers have strict SKU matching requirements for associated public IP addresses.
2
Evaluate the compatibility rules between Load Balancer SKUs and Public IP SKUs.
Standard Load Balancers require Standard SKU Public IPs, while Basic Load Balancers require Basic SKU Public IPs.
Mixing Basic and Standard SKUs between these resources is not supported in Azure.
3
Determine the cause of the public IP not being selectable in the portal.
The public IP must have been created as a Basic SKU IP, making it incompatible and thus hidden from the selection menu.
Azure portal filters out incompatible SKUs during configuration to prevent deployment errors.

Key Concept

SKU compatibility between Azure Load Balancer and Public IP addresses
Rate this question

Topics

Configure Azure Load Balancer

More questions from this topic