Does this meet the goal?

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have two Azure virtual networks named Vnet1 and Vnet2.

You have a Windows 10 device named Client1 that connects to Vnet1 by using a Point-to-Site (P2S) IKEv2 VPN.

You implement virtual network peering between Vnet1 and Vnet2. Vnet1 allows gateway transit.

Vnet2 can use the remote gateway.

You discover that Client1 cannot communicate with Vnet2.

You need to ensure that Client1 can communicate with Vnet2.

Solution: You download and reinstall the VPN client configuration.

Does this meet the goal?
A . Yes
B . No

View Answer

Answer: B

Explanation:

No, this solution does not meet the goal. Downloading and reinstalling the VPN client configuration on Client1 will not change the ability of Client1 to communicate with Vnet2. The ability for a P2S VPN client to communicate across a VNet peering connection depends on the configuration of the gateways and the network.

In this scenario, the virtual network peering is configured to allow gateway transit, and Vnet2 is set to use the remote gateway. However, you need to ensure that:

The VPN gateway for Vnet1 is configured to allow point-to-site clients to use Azure’s internal routing to access resources in Vnet2. This is typically allowed by default but should be verified.

Network security groups (NSGs) and/or route tables are not blocking the traffic from Client1 to Vnet2.

The address space of Vnet2 does not overlap with the address space for the P2S VPN clients. Azure uses the address space specified for the VPN client pool to route traffic from the clients through the gateway.

If all the above are correctly configured and Client1 still cannot communicate with Vnet2, you may need to check for any other routing issues or misconfigurations that might be preventing communication between the networks.