AZ-700 Question 45
Select 2You have two Azure Virtual Networks, VNetA and VNetB, both within the same subscription and with non-overlapping address spaces. VNetA contains a VPN gateway that provides a site-to-site connection to the on-premises network. You want all on-premises traffic to be able to reach both VNetA and VNetB via VNetA� gateway. You have decided to use VNet peering between VNetA and VNetB. Which two steps should you take so that on-premises traffic can access VNetB through the existing VPN gateway in VNetA?
- A
Enable 'Allow gateway transit' on VNetA� peering to VNetB
- B
Select 'Use remote gateways' in the peering from VNetB to VNetA
- C
Establish a separate site-to-site VPN connection from VNetB to the on-premises network
- D
Enable 'Allow forwarded traffic' in the peering settings on both VNetA and VNetB
Show answer and explanation
Correct answers: A, B
Explanation
To allow on-premises traffic to flow to a peer VNet via an existing VPN gateway, you must enable gateway transit on the VNet with the gateway (VNetA) and configure the other VNet (VNetB) to use the remote gateway. This setup ensures that on-premises traffic can be routed to all peer networks without establishing additional VPN connections. Refer to Azure documentation (https://learn.microsoft.com/azure/virtual-network/virtual-network-peering-overview) for details on VNet peering and gateway transit configurations.
- A. Correct.
Option 1 is correct because enabling 'Allow gateway transit' on VNetA� peering allows VNetB to leverage VNetA's VPN gateway for on-premises connectivity.
- B. Correct.
Option 2 is correct because selecting 'Use remote gateways' in VNetB� peering to VNetA routes VNetB traffic through the gateway in VNetA, providing on-premises access via the existing VPN connection.
- C. Incorrect.
Option 3 is incorrect. Creating a separate VPN connection for VNetB is unnecessary if VNetB is configured to use VNetA� gateway. This would also add complexity and cost.
- D. Incorrect.
Option 4 is incorrect. 'Allow forwarded traffic' is not specifically required for on-premises routing when using gateway transit. It is typically used in other forwarding scenarios, not this basic gateway transit scenario.