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.

• ✓

  Change VNet-B to a non-overlapping address space, such as 10.1.0.0/24.

  Why this is correct

  Azure VNet peering requires that the address spaces do not overlap. Changing VNet-B to a different range removes the conflict and allows peering to be created. The exact new range can vary, but it must not overlap with VNet-A’s 10.0.0.0/16 range.

• ✗

  Add a route table to VNet-B before creating the peering.

  Why it's wrong here

  Adding a route table to VNet-B cannot resolve the overlapping address-space conflict because Azure validates that peered VNet address spaces do not overlap when the peering is created. Route tables only influence data-plane traffic forwarding by specifying next-hop types, but the peering resource will fail to build with an 'Overlapping address spaces' error before any packet routing occurs. Consequently, no amount of custom user-defined routes can make peering succeed; the underlying CIDR blocks must first be made non-overlapping.

  When this WOULD be correct

  In a scenario where VNet peering is established but traffic fails to route correctly between subnets, adding a route table with specific routes (e.g., to force traffic through a firewall or VPN gateway) would be the correct solution.

• ✗

  Enable gateway transit on VNet-A.

  Why it's wrong here

  Enabling gateway transit on VNet-A configures the VNet to allow a peered VNet to use its VPN or ExpressRoute gateway, but this feature only becomes active after a peering link has been successfully established. Since VNet-A and VNet-B cannot be peered due to overlapping address spaces, there is no peering connection on which to enable transit, so the underlying conflict remains untouched. This option solves a routing and connectivity scenario for valid peerings, not the address allocation problem that blocks peering creation in the first place.

  When this WOULD be correct

  In a scenario where VNet-A needs to provide a VPN gateway to VNet-B for hybrid connectivity, and VNet-B does not have its own gateway, enabling gateway transit on VNet-A would allow VNet-B to use VNet-A's gateway.

• ✗

  Resize VNet-A to 10.0.0.0/15 so both VNets fit.

  Why it's wrong here

  Resizing VNet-A from 10.0.0.0/16 to 10.0.0.0/15 would broaden its address range to 10.0.0.0–10.1.255.255, which actually increases the overlap with VNet-B's range rather than eliminating it. Azure does not even permit resizing a VNet to a larger prefix that would overlap with another VNet that needs to be peered, and even if the change were allowed, the peering would still be rejected because both VNets would share addresses in the 10.0.x.x block. This change is therefore counterproductive—it exaggerates the exact problem the question asks to fix.

  When this WOULD be correct

  This option would be correct if the question asked for a change to allow both VNets to communicate via a VPN gateway or to accommodate more resources within VNet-A without overlapping with VNet-B, but the address spaces must be non-overlapping for peering.

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