You are implementing network connectivity between your on-premises network with two Azure virtual networks.
You configure your network with the addresses spaces below:
on-premises network: 10.0.1.0/16
vnet1 (Azure): 10.0.11.0/16
vnet2 (Azure): 10.0.12.0/16
You decide to implement a hub-spoke network topology to optimize the cost. You create a new virtual network named hub with the address space 10.0.10.0/16 and implement virtual network peering between vnet1 and hub, and vnet2 and the hub virtual network.
You need to complete the hub-spoke network topology configuration.
Which three actions should you perform?
You should perform the following actions:
Implement a VPN gateway on the hub virtual network.
Configure the peering connection on the hub virtual network to allow gateway transit.
Configure the peering connection on vnet1 and vnet2 to use remote gateways.
You should implement a VPN gateway on the hub virtual network. The hub virtual network centralizes connectivity to your on-premises network. You should implement a VPN gateway only on this virtual network. The spoke networks connects to on-premises through this hub network.
You should also configure the peering connection on the hub virtual network to allow gateway transit. This allows the on-premises network to access vnet1 and vnet2 virtual networks.
Finally, you should also configure the peering connections on vnet1 and vnet2 to use remote gateways. This allows the spoke networks to connect back with the on-premises network.
You should not implement a VPN gateway on the vnet1, vnet2, and hub virtual networks. You can configure network peering between Azure virtual networks by using a VPN gateway. However, you already configured virtual network peering between the virtual networks and the hub network. Implementing a VPN gateway in all virtual networks results is a more expensive solution.
You should not configure all peering connections to use remote gateways. You need to use remote gateways only in the spoke networks in a hub-spoke network topology, which, in this case, is vnet1 and vnet2.