AZ-700 Question 149
Single answerYour company has multiple on-premises locations that you want to connect to Azure using site-to-site VPN. You also require parallel connections using ExpressRoute for dedicated bandwidth, and plan to enable point-to-site VPN access for remote sales teams. Which Azure Virtual WAN SKU should you deploy to meet these requirements in a single, centrally managed setup?
- A
Deploy a Basic Virtual WAN to handle site-to-site VPN and ExpressRoute connections
- B
Deploy a Standard Virtual WAN to handle site-to-site VPN, user VPN, and ExpressRoute connectivity
- C
Deploy multiple Basic Virtual WAN resources, each dedicated to a specific on-premises location
- D
Use a custom Virtual WAN SKU created via Azure Resource Manager templates to handle advanced connectivity
Show answer and explanation
Correct answer: B
Explanation
Only the Standard Virtual WAN SKU supports the full range of connectivity scenarios including site-to-site VPN, ExpressRoute, and point-to-site VPN. According to Microsoft documentation (https://learn.microsoft.com/azure/virtual-wan/virtual-wan-about#sku-limitations), Basic skew does not allow ExpressRoute or user VPN functionality. Consequently, deploying Standard Virtual WAN is the correct choice for this scenario.
- A. Incorrect.
Incorrect. The Basic Virtual WAN SKU does not support user VPN or ExpressRoute connectivity, so it cannot meet the remote access and ExpressRoute requirements.
- B. Correct.
Correct. The Standard Virtual WAN SKU supports site-to-site VPNs, ExpressRoute connectivity, and user VPN, fulfilling this scenario� advanced connectivity needs.
- C. Incorrect.
Incorrect. Using multiple Basic Virtual WAN resources does not add user VPN or ExpressRoute support, as the Basic SKU fundamentally does not include those capabilities.
- D. Incorrect.
Incorrect. Azure currently only provides Basic and Standard SKUs for Virtual WAN; you cannot create a custom SKU to enable advanced features. All needed features are supported by the Standard SKU.