AVS Migration: Connection Type and Minimum Host Count?

Why the Answer Is Correct

Azure VMware Solution private clouds require a minimum of three ESXi hosts per cluster, which provides the redundancy and SLA that AVS demands; two hosts is below the supported minimum, and four or more hosts increases cost unnecessarily. For full integration between the AVS network, the on-premises VMware network, and other Azure virtual networks, ExpressRoute is the supported primary connection. ExpressRoute Global Reach connects the on-premises site to the AVS private cloud, and an ExpressRoute gateway connects the AVS private cloud to Azure virtual networks. This combination delivers private, predictable connectivity while keeping the host count at the cost-minimizing minimum.

Why Other Candidate Answers Are Wrong

Site-to-Site VPN is cheaper, but it is not supported as the primary AVS fabric connection and cannot provide the full integration across on-premises, AVS, and Azure VNets described in the requirement. Private Link is also unsuitable for the primary fabric connection because it is designed for private access to Azure PaaS services, not for AVS workload migration networking. Choosing two hosts fails the AVS minimum-cluster rule, and choosing four or more hosts violates the requirement to minimize costs when three hosts already satisfy the design.

Community Comment Notes

As mesloth noted, "Site-to-Site VPN and Private Link are not supported" as the primary fabric connection for AVS. That observation reinforces the ExpressRoute selection and rules out the cheaper VPN alternative that many candidates are tempted to choose.