mediummultiple choiceObjective-mapped

Two virtual networks were created in different subscriptions. VNet-A uses 10.4.0.0/16 and VNet-B uses 10.4.128.0/17. You try to create peering between them, but Azure rejects the request. What is the best fix?

Question 1mediummultiple choice
Full question →

Two virtual networks were created in different subscriptions. VNet-A uses 10.4.0.0/16 and VNet-B uses 10.4.128.0/17. You try to create peering between them, but Azure rejects the request. What is the best fix?

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

Enable gateway transit on both VNets before creating the peering.

Gateway transit does not solve overlapping address space conflicts during peering creation.

B

Distractor review

Add a route table to one VNet so the address spaces no longer overlap.

Route tables do not change IP address assignment, so the overlap still exists.

C

Best answer

Change one VNet to a non-overlapping address range, then create the peering again.

Azure virtual network peering requires non-overlapping address spaces, so renumbering is the correct fix.

D

Distractor review

Create a private endpoint between the two VNets instead of peering.

Private endpoints connect to supported services, not as a replacement for VNet-to-VNet peering.

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 one VNet to a non-overlapping address range, then create the peering again. — Azure virtual network peering requires the address spaces of the two VNets to be non-overlapping. Here, 10.4.0.0/16 contains 10.4.128.0/17, so peering cannot be established until one side is renumbered. After changing one VNet to a different, non-overlapping CIDR block, peering can be created and routes can be exchanged normally. Why others are wrong: Gateway transit settings help with shared gateway scenarios, but they do not bypass overlap restrictions. Route tables cannot change the underlying CIDR ranges, so they cannot fix address conflicts. Private endpoints are for reaching Azure PaaS services privately and are not a substitute for VNet-to-VNet connectivity.

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.