AZ-104 Practice Question 69: Peering Gateway Transit
Microsoft Azure Administrator Associate (AZ-104) · Test 7 · question 9 of 10
A hub VNet has a VPN gateway with a site-to-site connection to the on-premises network. A spoke VNet is peered with the hub, and VMs in the spoke can reach VMs in the hub but not the on-premises network. The company wants the spoke to use the hub's gateway and does not want to pay for a second gateway.
Which configuration change should the administrator make?
Show answer and explanation
Answer:
Gateway transit lets a peered VNet use the VPN or ExpressRoute gateway of the VNet it is peered with. The hub's side of the peering must have Allow gateway transit turned on, and the spoke's side must have Use remote gateways turned on. The spoke then routes on-premises traffic through the hub gateway, and no gateway is needed in the spoke. The spoke must not have its own gateway when it uses the remote one.
Option A does not add a route through the gateway. Allow forwarded traffic permits traffic that did not originate in the peered VNet to be accepted, but the spoke still has no path to the on-premises network without gateway transit.
Option C works but breaks the constraint. A second gateway costs money, and it is exactly what gateway transit avoids. It would also conflict with Use remote gateways on the same VNet.
Option D is about how routes are exchanged with the on-premises device. The missing piece is the spoke's ability to use the hub's gateway, and BGP does not provide it.
Reference: Virtual network peering