An organization has deployed a virtual network named `vnet-prod-uswest` (10.110.0.0/16) th… — Microsoft Azure Solutions Architect (AZ-305)

An organization has deployed a virtual network named `vnet-prod-uswest` ( $10.110.0.0/16$ ) that contains two subnets: `subnet-web` ( $10.110.1.0/24$ ) and `subnet-data` ( $10.110.2.0/24$ ). A Network Virtual Appliance (NVA) is deployed in a peered hub virtual network at $10.120.1.4$ .

The organization needs to inspect all traffic sent from `subnet-web` to `subnet-data` using the NVA. The solution must ensure that virtual machines within `subnet-web` can still communicate directly with each other without routing through the NVA.

Which route should be added to the route table associated with `subnet-web`?

Address prefix: $10.110.2.0/24$ , Next hop type: Virtual appliance, Next hop address: $10.120.1.4$ Cevap
B
Address prefix: $10.110.0.0/16$ , Next hop type: Virtual appliance, Next hop address: $10.120.1.4$
C
Address prefix: $10.110.1.0/24$ , Next hop type: Virtual appliance, Next hop address: $10.120.1.4$
D
Address prefix: $0.0.0.0/0$ , Next hop type: Virtual appliance, Next hop address: $10.120.1.4$

Cevap

Address prefix:

10.110.2.0/24

, Next hop type: Virtual appliance, Next hop address:

10.120.1.4

The correct route uses the destination prefix

10.110.2.0/24

, which matches only the database subnet. Because Azure uses the Longest Prefix Match algorithm, traffic destined for the database subnet will match this route and be forwarded to the NVA. Traffic destined for other resources within the same web subnet (

10.110.1.0/24

) will not match this route and will instead use the system-defined local route (

10.110.0.0/16

) with next hop 'Virtual Network', keeping the local communication direct.

Adım Adım Çözüm

Identify the destination subnet of the traffic that requires inspection.

The target traffic is destined for `subnet-data` which uses the prefix

10.110.2.0/24

Routing policies in Azure should target the most specific prefix possible to avoid affecting unrelated traffic paths.

Evaluate the priority and behavior of Azure system routes versus User-Defined Routes (UDRs).

Azure uses Longest Prefix Match (LPM) to select routes. If a UDR and a system route have identical prefixes, the UDR is preferred.

Understanding route selection order ensures the custom route is selected over the default system route.

Create a route that targets only the destination subnet and routes it to the NVA IP address.

A route with prefix

10.110.2.0/24

pointing to next hop

10.120.1.4

is associated with `subnet-web`.

Traffic to `subnet-data` (

10.110.2.0/24

) matches the UDR and goes to the NVA. Traffic within `subnet-web` (

10.110.1.x

) does not match the UDR prefix and falls back to the system route (

10.110.0.0/16

, next hop Virtual Network), keeping local traffic direct.

Anahtar Kavram

Azure route precedence rules and Longest Prefix Match (LPM) behavior with User-Defined Routes (UDRs)

Tahmini Süre:1m 30s

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular

Bu konudan daha fazla soru