A smart-grid utility provider is designing a telemetry ingestion system in the West US 3 region to collect real-time status updates from smart meters using a custom TCP protocol on port 8080. The design must satisfy the following requirements:
- Distribute incoming TCP traffic on port 8080 across a backend pool of virtual machines.
- Support high availability with zone-redundancy across three availability zones.
- Support the existing backend virtual machines, which currently have Basic SKU Public IP addresses assigned to their network interfaces.
Which of the following actions should you recommend to meet these requirements?
- Upgrade the virtual machines' public IP addresses to Standard SKU (or remove them), and deploy a Standard Load Balancer to distribute the TCP traffic.Cevap
- BDeploy a Standard Load Balancer to distribute the TCP traffic, and associate the backend virtual machines without modifying their existing Basic SKU public IP addresses.
- CDeploy a Basic Load Balancer to route the TCP traffic, and deploy all backend virtual machines in a single availability zone to accommodate the Basic SKU public IP addresses.
- DDeploy Azure Traffic Manager with a performance routing method to distribute the TCP traffic directly to the virtual machines across the availability zones.
Cevap
Upgrade the virtual machines' public IP addresses to Standard SKU (or remove them), and deploy a Standard Load Balancer to distribute the TCP traffic.
To support zone-redundancy across three availability zones, Azure Standard Load Balancer must be used because Basic Load Balancer is not zone-aware. However, Azure networking rules state that you cannot mix Basic and Standard SKU resources on the same virtual machine network interface. Therefore, the existing Basic SKU public IP addresses must be upgraded to Standard SKU (or removed) before the virtual machines can join the Standard Load Balancer backend pool.
Adım Adım Çözüm
Anahtar Kavram
Azure Load Balancer SKU alignment and zone-redundancy constraints