Examkin

Question

Difficulty: HardConfigure Virtual Network Peering

An administrator is configuring a hub-and-spoke network topology in Azure. The environment contains the following resources:

* A hub virtual network named VNet-Hub (10.100.0.0/1610.100.0.0/16) that contains a subnet named Subnet-Hub where a virtual machine named VM-Hub is deployed. VNet-Hub also contains an active virtual network gateway.
* A spoke virtual network named VNet-Spoke1 (10.101.0.0/1610.101.0.0/16) that contains a subnet named Subnet-Spoke1 where a virtual machine named VM-Spoke1 is deployed.
* A spoke virtual network named VNet-Spoke2 (10.102.0.0/1610.102.0.0/16) that contains a subnet named Subnet-Spoke2 where a virtual machine named VM-Spoke2 is deployed.

Virtual network peering is configured between VNet-Hub and VNet-Spoke1, and between VNet-Hub and VNet-Spoke2.

You need to configure the network to meet the following requirements:
1. VM-Spoke1 must be able to communicate with on-premises networks using the virtual network gateway in VNet-Hub.
2. VM-Spoke1 must be able to communicate directly with VM-Spoke2.
3. VM-Spoke2 must not be able to use the virtual network gateway in VNet-Hub.

Which three configurations should you implement? (Select THREE.)

  1. Configure a direct virtual network peering connection between VNet-Spoke1 and VNet-Spoke2.Answer
  2. On the peering connection from VNet-Hub to VNet-Spoke1, select the option to allow gateway transit.Answer
  3. On the peering connection from VNet-Spoke1 to VNet-Hub, select the option to use remote gateways.Answer
  4. D
    On the peering connection from VNet-Spoke2 to VNet-Hub, select the option to use remote gateways.
  5. E
    On the peering connection from VNet-Hub to VNet-Spoke1, select the option to allow forwarded traffic.
  6. F
    Configure no additional connections, as virtual network peering automatically routes traffic transitively through VNet-Hub.

Answer

To meet the requirements, you must configure a direct virtual network peering connection between VNet-Spoke1 and VNet-Spoke2, select 'Allow gateway transit' on the peering from VNet-Hub to VNet-Spoke1, and select 'Use remote gateways' on the peering from VNet-Spoke1 to VNet-Hub.
To satisfy the requirements, direct spoke-to-spoke communication must be established using a direct peering connection, as peering is non-transitive. Additionally, using VNet-Hub's gateway from VNet-Spoke1 requires enabling gateway transit on the hub-side peering and enabling remote gateways on the spoke-side peering. To prevent VNet-Spoke2 from using the gateway, the remote gateway setting must remain disabled on its peering connection.

Step-by-Step Solution

1
Address the communication requirement between VM-Spoke1 and VM-Spoke2.
Configure a direct virtual network peering connection between VNet-Spoke1 and VNet-Spoke2.
Because virtual network peering is non-transitive by default, VM-Spoke1 cannot communicate with VM-Spoke2 through VNet-Hub. A direct peering is required.
2
Allow VNet-Spoke1 to use VNet-Hub's gateway.
On the peering connection from VNet-Hub to VNet-Spoke1, select the option to allow gateway transit.
This configuration permits the virtual network gateway in the hub network to share its transit capability with the peered spoke network.
3
Enable the transit routing from VNet-Spoke1's side.
On the peering connection from VNet-Spoke1 to VNet-Hub, select the option to use remote gateways.
This configures VNet-Spoke1 to route on-premises bound traffic to the virtual network gateway in VNet-Hub.
4
Ensure VNet-Spoke2 cannot use VNet-Hub's gateway.
Do not select the option to use remote gateways on the peering connection from VNet-Spoke2 to VNet-Hub.
Leaving this setting disabled prevents VM-Spoke2 from sending transit traffic through the hub's virtual network gateway.

Key Concept

Virtual network peering transitivity and gateway transit configuration.
Rate this question

Topics

Configure Virtual Network Peering

More questions from this topic