User1 connects from home to gateway GW1 by using a Point-to-Site VPN from Computer1 (Windows 11) to access AppSvr1. After adding the listed resources, User1 cannot reach AppSvr2. What action will allow User1 to access AppSvr2?

When new resources are added to a virtual network that a Point-to-Site (P2S) VPN client connects to, the client's local routing table needs to be updated to include routes to these new resources. The simplest and most effective way to achieve this is by downloading and reinstalling the VPN client configuration package on Computer1. This package contains the updated routing information for the entire virtual network, including AppSvr2. Creating a route table and associating it with the GatewaySubnet on VNet1 is incorrect because the issue is with the client's ability to route to the new resource, not with the gateway itself. The gateway already knows about AppSvr2 if it's in the same VNet or peered. Changing the Windows Defender Firewall configuration on Computer1 is unlikely to be the solution unless the firewall was explicitly blocking traffic to AppSvr2, which is not implied by the scenario. Adding a service endpoint to VNet2 is irrelevant as service endpoints are used for securing Azure service traffic, not for P2S VPN client routing to VMs.