An organization is migrating a legacy high-throughput inventory application to Azure. The application uses a custom TCP-based protocol on port 8080. The architecture requires deploying three virtual machines (VMs) in a single Azure region, distributed across multiple Availability Zones to ensure zone redundancy. The VMs are currently associated with Basic SKU Public IP addresses. You need to design a load balancing solution to distribute the client TCP traffic to the VMs.
Which design action should you recommend?
- ADeploy a Standard Load Balancer to route traffic to the virtual machines using their existing Basic SKU public IP addresses.
- Reassociate the virtual machines with Standard SKU public IP addresses and deploy a Standard Load Balancer.Cevap
- CDeploy Azure Traffic Manager to route client TCP traffic directly to the virtual machines.
- DDeploy a Basic Load Balancer to load balance the TCP traffic across the virtual machines in all Availability Zones.
Cevap
Reassociate the virtual machines with Standard SKU public IP addresses and deploy a Standard Load Balancer.
To support virtual machines distributed across multiple Availability Zones, a Standard Load Balancer is required because a Basic Load Balancer does not support zone-redundant backend pools. Additionally, Azure requires SKU consistency, meaning virtual machines in a Standard Load Balancer's backend pool must be associated with Standard SKU public IP addresses rather than Basic SKU public IP addresses.
Adım Adım Çözüm
Anahtar Kavram
Azure Load Balancer SKU compatibility and Availability Zone support constraints.
Tahmini Süre:2m 0s