easymultiple choiceObjective-mapped

Exhibit

VNet-A address space: 10.0.0.0/16
VNet-B address space: 10.0.1.0/24
Attempt to peer VNet-A and VNet-B:
Status: Failed
Error: Address space overlap detected

Requirement: Both VNets must remain connected, but the address spaces must not overlap.

Based on the exhibit, what is the best change so the VNet peering can be created successfully?

Question 1easymultiple choice
Full question →

Based on the exhibit, what is the best change so the VNet peering can be created successfully?

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

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

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.

B

Distractor review

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

Route tables do not resolve overlapping address spaces. The peering fails before any routing behavior matters.

C

Distractor review

Enable gateway transit on VNet-A.

Gateway transit is used to share a VPN or ExpressRoute gateway through peering. It does not fix overlapping CIDR blocks.

D

Distractor review

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

Making the larger range would actually expand overlap instead of removing it. Peering still cannot be established when address spaces overlap.

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, such as 10.1.0.0/24. — The exhibit shows an overlap between 10.0.0.0/16 and 10.0.1.0/24, which is not allowed for VNet peering. The fix is to move one VNet to a different, non-overlapping address range. In practice, administrators choose a new CIDR block that does not conflict with existing networks, then recreate the peering. Why others are wrong: A route table, gateway transit, or resizing the larger VNet does not remove the overlap. Peering is blocked by the IP plan itself, so the network range must be corrected first. This is an address planning problem, not a routing or gateway problem.

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.