hardmultiple choiceObjective-mapped

A company is designing a hub-spoke network topology across multiple Azure regions. They plan to deploy a third-party network virtual appliance (NVA) in the hub for traffic inspection. They require that all traffic between spokes in different regions must be routed through the hub NVA, and they want to minimize the number of peered connections. Which solution should they implement?

Question 1hardmultiple choice
Full question →

A company is designing a hub-spoke network topology across multiple Azure regions. They plan to deploy a third-party network virtual appliance (NVA) in the hub for traffic inspection. They require that all traffic between spokes in different regions must be routed through the hub NVA, and they want to minimize the number of peered connections. Which solution should they implement?

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

Best answer

VNet peering with user-defined routes (UDRs) in each spoke pointing to the NVA IP in the hub

UDRs enforce traffic routing through the hub NVA; each spoke peers only to the hub, minimizing peering connections.

B

Distractor review

Azure Virtual WAN with a secured hub using Azure Firewall

Virtual WAN uses Azure Firewall, not a third-party NVA, and requires a different deployment model not aligned with the requirement.

C

Distractor review

Azure VNet-to-VNet VPN gateways between all spokes

This creates a full mesh of VPN connections, increasing complexity and cost, and does not route through the hub NVA.

D

Distractor review

Azure ExpressRoute with private peering

ExpressRoute is designed for on-premises to Azure connectivity, not for inter-spoke traffic within Azure.

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: VNet peering with user-defined routes (UDRs) in each spoke pointing to the NVA IP in the hub — Using VNet peering with user-defined routes (UDRs) in each spoke that force traffic destined to other spokes to go through the hub NVA's IP address is a common approach. This requires peering each spoke to the hub and configuring UDRs. Azure Virtual WAN with Azure Firewall is a managed alternative but uses Microsoft's firewall, not a third-party NVA. VPN gateways create full mesh, increasing connections. ExpressRoute is for on-premises connectivity.

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.