An organization is designing a regional high-availability solution in the East US region. The architecture requires deploying a Standard Load Balancer to distribute inbound traffic across three Azure Virtual Machines that are deployed across different Availability Zones. The virtual machines currently have Basic SKU Public IP addresses assigned to their network interfaces for direct administrative access. During validation of the backend pool configuration, the deployment fails.
To ensure the virtual machines can be successfully added to the Standard Load Balancer's backend pool while maintaining zone redundancy, which of the following actions should the architect recommend?
- Upgrade the public IP addresses of the virtual machines to the Standard SKU.Answer
- BDowngrade the Standard Load Balancer to a Basic Load Balancer to match the SKU of the virtual machines' public IP addresses.
- CDeploy Azure Traffic Manager to distribute traffic directly to the virtual machines' current Basic SKU Public IP addresses.
- DConfigure a Basic SKU Public IP prefix and associate it with the Standard Load Balancer's frontend IP configuration.
Answer
Upgrade the public IP addresses of the virtual machines to the Standard SKU.
The correct action is to upgrade the public IP addresses of the virtual machines to the Standard SKU. A Standard Load Balancer strictly requires that all virtual machines in its backend pool use the Standard SKU for any associated public IP addresses. This solution enables successful backend validation and retains support for Availability Zones and high availability.
Step-by-Step Solution
Key Concept
Standard SKU load balancers require all backend resources with public IP addresses to use the Standard SKU to ensure compatibility and support features like Availability Zones.