A multinational customer will connect their SD-WAN appliances to an Azure Virtual WAN VPN site. The network team must configure BGP so on-premises routes are learned by the virtual hub. Which of the following is the correct set of fields to configure on the Virtual WAN VPN site to enable BGP peering with their CPE?

To enable BGP peering between an Azure Virtual WAN VPN site and an on-premises SD-WAN appliance, you must configure the BGP peer ASN with the on-premises device's Autonomous System Number and the BGP peer IP with the IP address the CPE uses for BGP peering. The linkSpeedInMbps field should accurately reflect the physical tunnel bandwidth, as this value is used by Azure to determine the appropriate tunnel metrics and routing preferences. Incorrect options: Setting only the 'Azure ASN' and relying on autodiscovery is insufficient; the on-premises BGP peer IP and ASN must be explicitly configured. Link speed is relevant for performance and routing. Configuring a custom route table for BGP neighbors is not the primary mechanism for establishing BGP peering with a VPN site; the dedicated BGP settings are required. BGP over the public internet still requires ASN configuration. Using ExpressRoute gateway settings is incorrect as this scenario involves a VPN gateway, not ExpressRoute. BGP community strings are not the primary configuration for establishing basic BGP peering in this context.