You are managing the network resources for a web application. You deploy a Standard load balancer named LB1. You intend to add the network interfaces of two virtual machines, VM1 and VM2, to the backend pool of LB1. Both virtual machines currently have public IP addresses assigned to their network interfaces. However, when attempting to add the virtual machines to the backend pool of LB1, the operation fails with a compatibility error. You need to ensure both virtual machines can be added to the backend pool of LB1. What should you do?
- AConfigure virtual network peering between the subnets containing VM1 and VM2 to enable transitive routing.
- BChange the frontend IP configuration of LB1 to use a Basic SKU public IP address.
- Reconfigure the public IP addresses associated with the network interfaces of VM1 and VM2 to use the Standard SKU.Cevap
- DCreate a user-defined route (UDR) in the subnet route table to redirect frontend traffic directly to the private IP addresses of VM1 and VM2.
Cevap
Reconfigure the public IP addresses associated with the network interfaces of VM1 and VM2 to use the Standard SKU.
The correct configuration requires that all public IP addresses associated with resources in the backend pool of a Standard Load Balancer must match the Standard SKU of the load balancer itself. Reconfiguring the public IP addresses on the virtual machines' network interfaces to the Standard SKU satisfies this requirement and allows them to be added to the backend pool.
Adım Adım Çözüm
Anahtar Kavram
Standard Load Balancers require Standard SKU public IP addresses for all resources in their backend pool that have public IP associations. Standard and Basic SKUs cannot be mixed.