You are designing a regional TCP-based application infrastructure. You deploy a Standard Azure Load Balancer to distribute inbound traffic across a backend pool of Azure Virtual Machines in a single virtual network. However, when you attempt to add the virtual machines to the backend pool, the configuration fails validation. Which of the following is the most likely cause of this validation failure?
- The virtual machines are associated with Basic SKU public IP addresses.Answer
- BThe virtual machines are configured with User Defined Routes (UDRs) that overlap with the default Azure system routes.
- CThe configuration attempts to route traffic to the backend pool using an Azure Traffic Manager profile.
- DThe Network Security Group (NSG) on the subnet uses individual IP addresses instead of Service Tags for inbound rules.
Answer
The virtual machines are associated with Basic SKU public IP addresses.
The correct option is correct because Azure Standard Load Balancer requires all resources in the backend pool to match its SKU tier. If the virtual machines have Basic SKU public IP addresses attached to their network interfaces, the configuration will fail verification due to SKU mismatch constraints.
Step-by-Step Solution
Key Concept
Azure Load Balancer SKU boundary and compatibility constraints