Microsoft Azure Administrator Associate AZ-104
Get started today
Ultimate access to all questions.
In Subscription1, you have VNet1 with a static routing VPN gateway (VPNGW1) and a site-to-site VPN to an on-premises network. Client1, a Windows 10 machine, has a point-to-site VPN to VNet1. After setting up peering between VNet1 and VNet2 and confirming on-premises access to VNet2, Client1 cannot reach VNet2. What action will enable Client1 to connect to VNet2?
In Subscription1, you have VNet1 with a static routing VPN gateway (VPNGW1) and a site-to-site VPN to an on-premises network. Client1, a Windows 10 machine, has a point-to-site VPN to VNet1. After setting up peering between VNet1 and VNet2 and confirming on-premises access to VNet2, Client1 cannot reach VNet2. What action will enable Client1 to connect to VNet2?
Explanation:
The correct answer is A. If you change the topology of your network and have Windows VPN clients, the VPN client package for Windows must be downloaded and installed again. This is necessary to apply the changes to the client since it may now require new routing information due to the peering configuration. Therefore, reinstalling the VPN client configuration on Client1 will resolve the issue.