AZ-104 Question 26

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A1

  I'd keep the answer as Yes. Your point about the gateway settings is correct in general, but the question already shows those settings are in place. Why the peering is already configured The question says on-premises users can already reach VirtualNetworkB through VirtualNetworkA's gateway. That only works if Allow gateway transit is on for VirtualNetworkA and Use remote gateways is on for VirtualNetworkB. Gateway transit isn't limited to site-to-site traffic. It covers all traffic through that gateway, including P2S. Allow forwarded traffic isn't needed for gateway transit. It's for traffic from an NVA or another network being forwarded into the peered VNet. So on the Azure side, P2S traffic can already reach VirtualNetwork

• Chose B2

  A point‑to‑site (P2S) VPN connection terminates on VirtualNetworkA’s VPN gateway, not on VirtualNetworkB. Even though VNet peering exists between A and B, P2S traffic does NOT automatically flow across peered VNets unless: The gateway is configured to allow forwarded traffic, and UseRemoteGateways and AllowGatewayTransit are both configured on the peering. Simply re‑installing the VPN client package does nothing to enable routing to VirtualNetworkB.

• Chose B2

  The correct answer is B. Reinstalling the VPN client doesn't solve the problem