Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft Certified: Azure Network Engineer Associate · Microsoft
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
To migrate your hub-and-spoke topology to Azure Virtual WAN while maintaining a single point of ingress from the internet: Add virtual network peerings (B): This will help connect your existing virtual networks to the Virtual WAN hub, ensuring seamless communication between them. Create virtual network connections (D): This is necessary to establish connectivity between your virtual networks and the Virtual WAN hub. Remove the existing virtual network peerings (E): Since Virtual WAN will handle the connectivity, the existing peerings are no longer needed and should be removed to avoid conflicts.
The answers are correct. They're specifically listed order on this page: https://learn.microsoft.com/en-us/azure/virtual-wan/migrate-from-hub-spoke-topology#step-5-transition-connectivity-to-virtual-wan-hub a. Delete the existing peering connections from Spoke virtual networks to the old customer-managed hub. Access to applications in spoke virtual networks is unavailable until steps a-c are complete. b. Connect the spoke virtual networks to the Virtual WAN hub via VNet connections. c. Remove any user-defined routes (UDR) previously used within spoke virtual networks for spoke-to-spoke communications. This path is now enabled by dynamic routing available within the Virtual WAN hub.
Thanks for including the link. The Q is way too ambiguous and doesn't mention existing topology at all. It only mentions a hub so you have to assume there are spokes with peerings and the AGW is in one of those.