A healthcare provider is deploying a regional medical records synchronization service on virtual machines in a single Azure region. The service requires low-latency TCP communication on port 5000, does not require SSL/TLS termination, and does not require URL-based routing. To distribute traffic, the provider attempts to configure an Azure Standard Load Balancer. However, the deployment fails because the backend virtual machines are associated with Basic SKU public IP addresses.
Which action should you recommend to resolve the deployment failure while meeting all service requirements?
- Upgrade the public IP addresses of the virtual machines to the Standard SKU.Answer
- BReplace the load balancer with an Azure Application Gateway instance.
- CReplace the load balancer with an Azure Front Door profile.
- DReplace the load balancer with an Azure Traffic Manager profile.
Answer
Upgrade the public IP addresses of the virtual machines to the Standard SKU.
Upgrading the public IP addresses of the virtual machines to the Standard SKU is the correct solution. Standard Load Balancer backend pools require Standard SKU IP addresses. This change satisfies the validation constraint while keeping the layer-4 TCP load balancing architecture intact to support the port 5000 service requirement.
Step-by-Step Solution
Key Concept
Azure Load Balancer SKU alignment and protocol routing constraints