A company is deploying a regional backend database service on Azure Virtual Machines in the East US region. The virtual machines require direct inbound internet access for management, which is currently enabled via Basic SKU public IP addresses assigned to their network interfaces. You need to design a load balancing solution using a regional Azure Standard Load Balancer to distribute custom TCP database traffic across these virtual machines. During the deployment, you encounter validation errors when configuring the backend pool. Which action should you recommend to resolve the validation errors?
- AConfigure the Standard Load Balancer frontend to use a Basic SKU public IP address.
- BDeploy Azure Traffic Manager to distribute the TCP database traffic directly to the virtual machines.
- Upgrade the public IP addresses assigned to the virtual machines' network interfaces to the Standard SKU.Answer
- DDeploy a Basic Load Balancer and configure it as a frontend proxy for the Standard Load Balancer.
Answer
Upgrade the public IP addresses assigned to the virtual machines' network interfaces to the Standard SKU.
The correct action is to upgrade the public IP addresses assigned to the virtual machines to the Standard SKU. Azure Standard Load Balancers require all associated resources, including the virtual machines in the backend pool and any public IP addresses assigned directly to their network interfaces, to use the Standard SKU. Mixing Basic and Standard SKUs within the same load balancer configuration is not supported and causes deployment validation failures.
Step-by-Step Solution
Key Concept
SKU compatibility requirements for Azure Standard Load Balancer.
Estimated Time:2m 0s