Subscription1 contains VNet1 and VNet2. VNet1 has a static-route VPN gateway (VPNGW1) and a site-to-site VPN to your on-premises network. Client1 (Windows 10) has a point-to-site VPN to VNet1. VNet1 and VNet2 are peered, and on-premises clients can reach VNet2, but Client1 cannot. What should you do to allow Client1 to connect to VNet2?

The correct answer is to download and re-install the VPN client configuration package on Client1. When VNet peering is configured with gateway transit enabled, the VPN client configuration package needs to be regenerated and reinstalled on the client. This updates the client's routing table to include routes to the peered VNet (VNet2 in this case), allowing Client1 to access resources in VNet2 through VNet1's VPN gateway. Selecting "Use the remote virtual network's gateway or Route Server" on either VNet1 to VNet2 or VNet2 to VNet1 peering is necessary for gateway transit, but it's not the final step for the client. The client configuration must be updated after this setting is applied. Enabling BGP on VPNGW1 is not directly relevant to a static-route VPN gateway or to enabling P2S client access to a peered VNet; BGP is for dynamic routing.