Examkin

Soru

Zorluk: KolayConfigure Virtual Network Peering

An organization deploys three Azure virtual networks in the East US region: `VNet-Alpha` (172.16.0.0/16172.16.0.0/16), `VNet-Beta` (172.17.0.0/16172.17.0.0/16), and `VNet-Gamma` (172.18.0.0/16172.18.0.0/16). Virtual machines are running within the subnets of each virtual network.

You establish a virtual network peering link between `VNet-Alpha` and `VNet-Beta`. Next, you establish a virtual network peering link between `VNet-Beta` and `VNet-Gamma`.

The peering configurations have 'Allow forwarded traffic' enabled, and 'Use remote gateways' and 'Allow gateway transit' are disabled. There are no virtual network gateways or network virtual appliances in any of the virtual networks.

What is the resulting connectivity between the virtual machines in `VNet-Alpha` and the virtual machines in `VNet-Gamma`?

  1. A
    The virtual machines can communicate directly because virtual network peering is transitive when 'Allow forwarded traffic' is enabled.
  2. The virtual machines cannot communicate because virtual network peering is non-transitive, and there is no gateway or network virtual appliance to route traffic between them.Cevap
  3. C
    The virtual machines can communicate only if 'Allow gateway transit' is enabled on both peering links, which automatically routes traffic through the transit network.
  4. D
    The virtual machines can communicate because 'Allow forwarded traffic' is enabled, which automatically routes transit traffic through the intermediate virtual network.

Cevap

The virtual machines cannot communicate because virtual network peering is non-transitive, and there is no gateway or network virtual appliance to route traffic between them.
The correct answer is correct because Azure virtual network peering is non-transitive. Peering VNet-Alpha to VNet-Beta and VNet-Beta to VNet-Gamma does not allow resources in VNet-Alpha to reach VNet-Gamma. For transit routing to occur, a gateway or a network virtual appliance (NVA) must be present in VNet-Beta, and the peering settings must be configured to allow gateway transit or transit routing.

Adım Adım Çözüm

1
Analyze the topology and peering configuration between the virtual networks.
VNet-Alpha is peered with VNet-Beta, and VNet-Beta is peered with VNet-Gamma, creating a linear chain.
To determine connectivity, the relationships between all networks must be mapped.
2
Check the transitivity of Azure virtual network peering.
Azure virtual network peering is non-transitive by default.
Traffic does not flow automatically from one peered network through a middle network to reach a third network.
3
Verify if any transit mechanisms are deployed to enable routing.
There are no virtual network gateways or network virtual appliances (NVAs) configured to route transit traffic.
Without these transit mechanisms, communication between the non-peered networks at the ends of the chain is impossible.

Anahtar Kavram

Virtual network peering in Azure is non-transitive. To route traffic through an intermediate virtual network, you must use a virtual network gateway or a network virtual appliance (NVA) along with user-defined routing.
Tahmini Süre:1m 0s
Bu soruyu puanla

Konular

Configure Virtual Network Peering

Bu konudan daha fazla soru