easymultiple choiceObjective-mapped

Exhibit

Hub VNet address space: 10.20.0.0/16
Spoke VNet address space: 10.20.1.0/24
Planned action: Create VNet peering between Hub and Spoke
Portal message: The address spaces overlap and cannot be peered.

Based on the exhibit, what should the administrator do so the hub and spoke can be peered successfully?

Question 1easymultiple choice
Full question →

Based on the exhibit, what should the administrator do so the hub and spoke can be peered 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

Distractor review

Keep the current ranges and enable gateway transit on the peering.

Gateway transit helps shared routing through a gateway, but it does not fix overlapping address spaces.

B

Best answer

Change the spoke VNet to a non-overlapping address space.

Azure VNet peering requires unique, non-overlapping IP ranges. Changing the spoke to a different CIDR block resolves the conflict and allows the peering to be created.

C

Distractor review

Add another subnet inside the spoke VNet and reuse the current address space.

Adding more subnets does not remove overlap. The entire VNet address space still conflicts with the hub network.

D

Distractor review

Create a network security group on the spoke subnet before peering.

NSGs control traffic filtering, but they do not affect whether two virtual networks can be peered.

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 the spoke VNet to a non-overlapping address space. — Azure rejects VNet peering when the address spaces overlap. In this exhibit, both networks use ranges within 10.20.0.0/16, so the spoke must be renumbered to a different, non-overlapping CIDR block before peering. Once the address space is unique, the administrator can create the peering relationship normally. Why others are wrong: Gateway transit, extra subnets, and NSGs do not solve address overlap. The problem is at the VNet address-space level, not routing or filtering. Azure will continue to block peering until the spoke network uses a different range.

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.