VNet1 contains subnets Gateway, Perimeter, NVA, and Production. Two NVAs in the NVA subnet inspect traffic between Perimeter and Production. You must deploy an Azure load balancer so the NVAs run active‑active with automatic failover and load balance traffic to two services on the Production subnet that use different IP addresses. Which three actions should you perform?

A Standard Load Balancer is required because it supports HA Ports, which are essential for active-active NVA deployments and load balancing across multiple ports and IP addresses. Basic Load Balancers do not support HA Ports. To load balance traffic to two services on the Production subnet using different IP addresses, you need two separate load balancing rules. Enabling HA Ports on these rules allows the load balancer to distribute traffic across all ports, which is crucial for NVA scenarios. Floating IP (Direct Server Return) must be enabled to ensure the source IP address is preserved for the backend services, which is often a requirement for NVA deployments. A frontend IP configuration defines the IP address clients connect to. Two backend pools are needed, one for each NVA, to distribute traffic between them. A health probe monitors the health of the NVAs, ensuring traffic is only sent to healthy instances.