hardmultiple choiceObjective-mapped

A company has a hub-spoke network topology in Azure. They have multiple spoke VNets connected to a hub VNet via peering. They need to ensure that all east-west traffic between spoke VNets goes through a network virtual appliance (NVA) in the hub for inspection. Additionally, all outbound internet traffic from spoke VMs must use a single public IP address. What should they configure?

Question 1hardmultiple choice
Full question →

A company has a hub-spoke network topology in Azure. They have multiple spoke VNets connected to a hub VNet via peering. They need to ensure that all east-west traffic between spoke VNets goes through a network virtual appliance (NVA) in the hub for inspection. Additionally, all outbound internet traffic from spoke VMs must use a single public IP address. What should they configure?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Configure spoke VNets with a default route to the NVA IP, and deploy a NAT gateway in the hub for outbound traffic.

A default route would send all traffic to the NVA, including internet traffic, but NAT gateway is not the correct way to route internet traffic through the NVA. Also, east-west traffic routing requires specific UDRs for other spoke address ranges.

B

Distractor review

Configure a route table in each spoke with a route to the hub NVA for inter-spoke traffic, and use Azure Firewall in the hub for outbound internet traffic.

This is partially correct but missing the need to enable 'Allow forwarded traffic' on peering. Without that, the NVA cannot forward packets between spokes even with UDRs. However, this is still a plausible but incomplete answer. Option D is more complete.

C

Distractor review

Enable 'Allow gateway transit' on the hub VNet and 'Use remote gateways' on the spoke VNets for the NVA.

Gateway transit is a feature for VPN/ExpressRoute gateways, not for NVAs. NVAs require UDRs and forwarded traffic settings, not gateway transit.

D

Best answer

Configure VNet peering with 'Allow forwarded traffic' enabled, add user-defined routes in each spoke pointing to the NVA IP for inter-spoke traffic, and use Azure Firewall in the hub for outbound internet with a default route in spokes.

This combination correctly routes east-west traffic through the NVA using UDRs and 'Allow forwarded traffic'. For outbound, Azure Firewall provides a single public IP and UDRs direct internet traffic to it.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Related practice questions

Related AZ-305 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-305 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Configure VNet peering with 'Allow forwarded traffic' enabled, add user-defined routes in each spoke pointing to the NVA IP for inter-spoke traffic, and use Azure Firewall in the hub for outbound internet with a default route in spokes. — To route east-west traffic through the NVA, you need to configure user-defined routes (UDRs) in each spoke VNet that point the traffic destined for other spoke VNet address spaces to the NVA's IP address. You also must enable 'Allow forwarded traffic' on the VNet peering connection from the hub to the spokes so that the NVA can forward traffic. For outbound internet traffic, you can deploy Azure Firewall in the hub and configure a default route (0.0.0.0/0) in the spokes pointing to Azure Firewall (or the NVA if it also does NAT). Azure Firewall can provide a single public IP for all outbound traffic. Option D correctly describes these components. Option A uses NAT gateway which works for outbound but does not route east-west traffic through the NVA. Option B mentions Azure Firewall for outbound but lacks the specific route configuration for east-west. Option C assumes gateway transit, but NVA is not a VPN gateway.

What should I do if I get this AZ-305 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.