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.
To connect Vnet2 and Vnet3 with gateway transit, you need to ensure both virtual networks (Vnet2 and Vnet3) can use the gateway in a peered virtual network. Therefore, on the peerings from Vnet2 and Vnet3, you should select 'Use remote gateways' to use the gateway in another VNet. Additionally, 'Allow gateway transit' must be enabled on the peerings from Vnet2 and Vnet3 to allow Vnet2 and Vnet3 to use the gateway for routing traffic to on-premises networks or other connected VNets.
You cannot select Gateway transit on peering on vnet1 - only allow traffic forwarded from remote virtual network
Agree with Zika69
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
Maybe they have changed the settings name or they are referring to a so-called 'gateway transit'. Again, Microsoft makes a lot of confusion with the exam questions. There is no gateway transit as a settings now, you can check below, so the right ones are B and E in my opinion. https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-peering-gateway-transit
vnets 2 and 3 need to peer with vnet1.
In exam Feb, 2023
A and B are the correct answer
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
- 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
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
AWS as well
The sentence should be modified without creating confusion
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
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.
Allow gateway transit is not applicable on vnet1 peering. There is no hub here.
On the peering from VNet1, select Allow forwarded traffic: • This would allow traffic to be forwarded between peered VNets, but it doesn’t directly address the issue of connecting VNet2 and VNet3 through a gateway. It’s useful for other use cases like enabling traffic from VMs across VNet peering, but not directly applicable for enabling gateway transit.