mediummultiple choiceObjective-mapped

A company wants to peer a new spoke virtual network to an existing hub VNet. The hub uses 10.40.0.0/16, and the new spoke was created with 10.40.128.0/17 because that range seemed available in the branch office plan. Peering creation fails. What should the administrator do?

Question 1mediummultiple choice
Full question →

A company wants to peer a new spoke virtual network to an existing hub VNet. The hub uses 10.40.0.0/16, and the new spoke was created with 10.40.128.0/17 because that range seemed available in the branch office plan. Peering creation fails. What should the administrator do?

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 second address prefix to the spoke VNet and keep the overlapping range.

Adding another prefix does not fix the overlap. The overlapping prefix must be removed or replaced with a non-overlapping range.

B

Best answer

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

Azure VNet peering requires non-overlapping IP ranges. The spoke must use an address space that does not conflict with the hub or any connected network.

C

Distractor review

Enable gateway transit on the hub VNet before retrying peering.

Gateway transit affects routing through a gateway, but it does not allow overlapping address spaces for peering.

D

Distractor review

Create custom DNS records for the spoke VNet so the address ranges no longer conflict.

DNS has no effect on IP range overlap. Peering validation is based on IP space, not name resolution.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

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?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Change the spoke VNet to a non-overlapping address space before peering. — VNet peering cannot be created when the address spaces overlap. The spoke currently uses 10.40.128.0/17, which falls inside the hub's 10.40.0.0/16 range. The correct fix is to redesign the spoke with a non-overlapping address space before deployment or peering. This is a planning issue, not a routing or DNS configuration issue. Why others are wrong: Adding more prefixes does not remove the conflict. Gateway transit is only relevant after peering is already valid. DNS records do not influence peering validation or routing between address spaces, so they cannot solve an overlap 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.