You have a hub-and-spoke network where multiple on-premises sites connect to a hub virtual network in Azure using ExpressRoute circuits. An Azure Application Gateway named GW1 serves as the single internet ingress point. You plan to move the hub-and-spoke design to Azure Virtual WAN while preserving a single point of ingress. Which three changes must you include in the migration? Select three.

Migrating to Azure Virtual WAN (vWAN) fundamentally changes how routing and connectivity are managed. 1. Remove the existing virtual network peerings: In a traditional hub-and-spoke, VNet peerings connect spokes to the hub. vWAN uses a different architecture where spokes connect to the vWAN hub via virtual network connections, making traditional peerings redundant and potentially conflicting. 2. Create virtual network connections: This is the core method for connecting spoke VNets to the vWAN hub. Each spoke VNet will require a virtual network connection to the vWAN hub to establish connectivity. 3. Replace the user-defined routes used by the current topology: Existing UDRs in the spokes likely point to the traditional hub's firewall or VPN gateway. With vWAN, routing is largely handled by the vWAN hub, and UDRs in spokes will need to be updated or removed to direct traffic correctly through the vWAN hub. Adding UDRs (without specifying replacement) or adding virtual network peerings would conflict with the vWAN model. Redeploying GW1 is unnecessary as Application Gateways can integrate with vWAN without redeployment.