Bitzu

AZ-305 ยท Hybrid networking and network security

Hub-and-spoke network topology

Hub-and-spoke with VNet peering and gateway transit versus Azure Virtual WAN, IP address planning, user-defined routes to force traffic through a firewall.

Key points

  • Hub VNet: VPN or ExpressRoute gateway, Azure Firewall, Bastion, DNS; spokes peer to it.
  • Peering is non-transitive: spoke-to-spoke needs peering or UDRs through the hub firewall.
  • Gateway transit: hub allows gateway transit, spoke uses remote gateway; allow forwarded traffic.
  • Non-overlapping address spaces; one hub per region.
  • Azure Virtual WAN: Microsoft-managed hub; own hub: more control over NVAs and costs.

Source: https://learn.microsoft.com/en-us/azure/architecture/networking/architecture/hub-spoke

Practice questions

Single choice

Spokes must reach on-premises through the VPN gateway in the hub. Which setting do you enable on the hub side of each peering?

  1. Use the remote virtual network's gateway
  2. Allow gateway transit
  3. Allow forwarded traffic only
  4. Disable virtual network access
Show answer

Answer: B. Allow gateway transit

The hub peering must allow gateway transit so that spokes can borrow its gateway. 'Use the remote virtual network's gateway' is the matching setting on the spoke side, not the hub side. Forwarded traffic is about traffic relayed by an appliance, not about sharing a gateway.

Select all that apply

Which statements about a customer-managed hub-and-spoke design are correct?

  1. VNet peering is non-transitive
  2. Spokes can sit in different subscriptions than the hub
  3. Two spokes peered to one hub can talk without extra setup
  4. Plan one hub per region and attach spokes from that region
  5. Peered VNets may reuse the same address space
Show answer

Answer: A. VNet peering is non-transitive, B. Spokes can sit in different subscriptions than the hub, D. Plan one hub per region and attach spokes from that region

Peering is non-transitive; spokes can live in other subscriptions (even other Entra tenants); and the hub is a regional resource, so the guidance is one hub per region with spokes from that region. Spokes do not automatically reach each other through the hub, and peered address spaces must not overlap.

True or false

If spoke A and spoke B are each peered with the same hub, VMs in spoke A can reach VMs in spoke B without any further configuration.

Show answer

Answer: False

False. VNet peering is non-transitive. Spoke-to-spoke traffic needs a direct peering (or a Virtual Network Manager connected group) or routing through a hub firewall or NVA with UDRs.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More AZ-305 topics in this module