You need to connect Vnet2 and Vnet3. The solution must meet the virtual networking requirements and the business requirements.
Which two actions should you include in the solution? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
AB
Virtual network peering seamlessly connects two Azure virtual networks, merging the two virtual networks into one for connectivity purposes. Gateway transit is a peering property that lets one virtual network use the VPN gateway in the peered virtual network for cross-premises or VNet-to-VNet connectivity. The following diagram shows how gateway transit works with virtual network peering.
In the diagram, gateway transit allows the peered virtual networks to use the Azure VPN gateway in Hub-RM. Connectivity available on the VPN gateway, including S2S, P2S, and VNet-to-VNet connections,
Reference:
https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-peering-gateway-transit
You cannot select Gateway transit on peering on vnet1 - only allow traffic forwarded from remote virtual network
Agree with Zika69
In exam Feb, 2023
vnets 2 and 3 need to peer with vnet1.
AB To use virtual network peerings, in the virtual network Peering setup: - Configure the peering connection in the hub to Allow gateway transit. - Configure the peering connection in each spoke to Use the remote virtual network's gateway. - Configure all peering connections to Allow forwarded traffic. https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/hybrid-networking/hub-spoke?tabs=cli#spoke-connections-to-remote-networks-through-a-hub-gateway
There's no option "gateway transit." in the peering configuration. Three's only "traffic forwarded from remote virtual network"
We can use "AllowGatewayTransit" in PowerShell command for peering configuration
A and B are the correct answer
Allow gateway transit is not applicable on vnet1 peering. There is no hub here.
Looks like that question could be old. https://azure.microsoft.com/fr-fr/blog/create-a-transit-vnet-using-vnet-peering/ In that blog we can see the option "allow gateway transit" on hub-to-spoke peering.
- If you consider that all the steps are being performed on the portal, there is no "Allow Gateway Transit" to be "Selected" as described in the article below: https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-peering-gateway-transit#to-add-a-peering-and-enable-transit - If you consider all the steps are being performed in PowerShell, using "Add-AzVirtualNetworkPeering" command, so, you have the attribute "-AllowGatewayTransit" to be "Set" not "Selected", since its a boolean option. https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-peering-gateway-transit#ps-same
AB correct however from peering perspective .. There is no mention of FW/RouteServer/NVA in the Vnet 1...so assume the VNET2 and VNET3 will learn the route from the GW
The sentence should be modified without creating confusion
There is no such thing as gateway transit option in VPC peering gateway transit is the feature
VPC is in GCP cloud
AWS as well