mediummultiple choiceObjective-mapped

An administrator plans to peer VNet-A with VNet-B so two application tiers can communicate over private IPs. VNet-A uses 10.20.0.0/16. VNet-B currently uses 10.20.1.0/24, and both VNets already contain subnets that must remain intact. The peering operation fails. What should the administrator do first?

Question 1mediummultiple choice
Full question →

An administrator plans to peer VNet-A with VNet-B so two application tiers can communicate over private IPs. VNet-A uses 10.20.0.0/16. VNet-B currently uses 10.20.1.0/24, and both VNets already contain subnets that must remain intact. The peering operation fails. What should the administrator do first?

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

Add a route table to VNet-B so traffic can bypass the overlap.

Route tables affect traffic flow after networking is established, but they do not resolve overlapping address spaces between VNets.

B

Best answer

Change VNet-B to a non-overlapping address space before creating the peering.

Azure VNet peering requires that the peered VNets use non-overlapping IP address ranges. Because VNet-B overlaps with VNet-A, the peering cannot be created successfully until one side is renumbered. The safest first step is to plan and apply a new, unique CIDR block for VNet-B that does not conflict with any existing subnet or on-premises range. Once the address spaces are non-overlapping, peering can be created and private connectivity can work as intended.

C

Distractor review

Create a network security group rule to allow all traffic between the VNets.

NSG rules control allowed ports and protocols, but they do not fix overlapping CIDR ranges or enable peering creation.

D

Distractor review

Enable gateway transit on VNet-A so the address conflict is ignored.

Gateway transit supports routing through a VPN or ExpressRoute gateway, but it does not bypass the peering requirement for unique address spaces.

Common exam trap

Common exam trap: usable hosts are not the same as total addresses

Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.

Technical deep dive

How to think about this question

Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.

KKey Concepts to Remember

  • CIDR notation defines the prefix length.
  • Block size helps identify subnet boundaries.
  • Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
  • The required host count determines the smallest suitable subnet.

TExam Day Tips

  • Write the block size before choosing the subnet.
  • Check whether the question asks for hosts, subnets or a specific address range.
  • Do not confuse /24, /25, /26 and /27 host counts.

Related practice questions

Related AZ-104 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-104 question test?

CIDR notation defines the prefix length.

What is the correct answer to this question?

The correct answer is: Change VNet-B to a non-overlapping address space before creating the peering. — VNet peering only works when each virtual network has a unique, non-overlapping address space. In this scenario, the two VNets both use parts of 10.20.0.0/16, so Azure rejects the peering request. The administrator must renumber one network before the relationship can be created. After the address ranges are fixed, traffic can flow over the Microsoft backbone using private IPs without adding extra routing components. Why others are wrong: A route table or NSG rule cannot repair overlapping IP space; those controls apply after connectivity exists. Gateway transit is meant for using a gateway across peerings, not for ignoring CIDR conflicts. The fundamental blocker here is the IP plan, so renumbering one VNet is the only valid first step.

What should I do if I get this AZ-104 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.