AZ-104 Implement and Manage Virtual Networking Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  10.0.1.0/24

  Why it's wrong here

  This address range falls entirely within the hub VNet's address space (assuming a hub like 10.0.0.0/16), causing an overlapping IP space. Azure virtual network peering requires that neither VNet's address space can overlap with the other's, otherwise peering fails or routing becomes ambiguous. Additionally, a single /24 provides only 251 host addresses, which is too restrictive for a spoke intended to host dozens or hundreds of VMs across multiple subnets.

  When this WOULD be correct

  If the hub VNet used a different address space (e.g., 10.1.0.0/16) and the on-premises range was 10.2.0.0/16, then 10.0.1.0/24 would be a non-overlapping choice for a small spoke.

• ✗

  10.1.0.0/22

  Why it's wrong here

  While this range does not overlap the hub VNet, it overlaps the on-premises corporate network address range, which is commonly connected via hub VPN gateway or ExpressRoute. In a hub-spoke topology, the spoke relies on the hub to route to on-premises; any overlapping prefix creates a routing conflict, causing traffic to be sent locally instead of through the hub or resulting in asymmetric routing. This violates the requirement for unique, non-conflicting address spaces across the entire connected topology, not just between peered VNets.

  When this WOULD be correct

  If the on-premises range were different (e.g., 10.3.0.0/16) and the hub VNet used 10.0.0.0/16, then 10.1.0.0/22 would be a non-overlapping choice that provides sufficient IP addresses for the required subnets.

• ✓

  10.2.0.0/22

  Why this is correct

  This address space does not overlap the hub or on-premises ranges and is large enough to carve out two usable subnets for the workload. A /22 gives room for multiple subnets and future growth, which is important when planning a spoke that needs to host dozens or hundreds of VMs. It is a practical choice for peering compatibility and capacity.

• ✗

  10.0.0.0/24

  Why it's wrong here

  This is part of the hub's own address space, specifically the first /24 of a typical 10.0.0.0/16, so using it for the spoke would create a direct IP address overlap that prevents peering. Azure VNet peering enforces that address spaces are disjoint, and any nested or identical CIDR blocks are rejected. Moreover, it is far too small to support a spoke with multiple subnets, as a /24 only supports about 251 usable IPs, and it would also conflict with any hub subnets already allocated from that range.

  When this WOULD be correct

  This option would be correct if the hub VNet used a different address space (e.g., 10.1.0.0/16) and the spoke needed a small subnet (e.g., for 120 VMs) with no on-premises overlap, and the question asked for a minimal non-overlapping /24 within 10.0.0.0/16.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Go deeper

Related to this question