Microsoft Certified: Azure Administrator AssociateImplement and manage virtual networkingEasy
A company has two Azure Virtual Networks (VNets), 'VNetA' and 'VNetB', located in different Azure regions. 'VNetA' is in 'West US 2' and 'VNetB' is in 'East US'. They need to enable direct and private communication between virtual machines (VMs) in 'VNetA' and 'VNetB'. Which networking feature should you implement?
- AAzure Private Link
- BVNet peering
- CVPN Gateway
- DAzure Virtual WAN
Show answer & explanationAnswer & explanation
Correct answer: B. VNet peering
VNet peering allows you to seamlessly connect two or more Azure Virtual Networks. The VNets appear as one for connectivity purposes. Global VNet peering supports connecting VNets across different Azure regions, enabling direct and private communication between them.
Why the other options are wrong
- A. Azure Private Link provides private connectivity to Azure PaaS services or customer-owned services hosted in Azure, not for VNet-to-VNet communication.
- C. A VPN Gateway can connect VNets, but VNet peering offers a simpler, lower-latency, and higher-bandwidth solution for VNet-to-VNet communication within Azure.
- D. Azure Virtual WAN is a networking service that provides optimized, automated, and global branch-to-branch connectivity. While it can connect VNets, VNet peering is the more direct and simpler solution for connecting just two VNets.
VNet Peering
A mechanism to connect two or more Azure Virtual Networks, making them appear as one for connectivity, enabling direct and private communication.
- Supports peering within the same region (Local VNet Peering) or across regions (Global VNet Peering).
- Traffic between peered VNets uses the Microsoft backbone network and does not traverse the public internet.
- Provides high-bandwidth, low-latency connectivity.
Memory trick: Peering: Like holding hands between VNets.