AZ-104 Implement and Manage Virtual Networking Practice Question
This AZ-104 practice question tests your understanding of implement and manage virtual networking. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
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.
A
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
Add a route table to VNet-B before creating the peering.
Why wrong: Route tables do not resolve overlapping address spaces. The peering fails before any routing behavior matters.
C
Enable gateway transit on VNet-A.
Why wrong: Gateway transit is used to share a VPN or ExpressRoute gateway through peering. It does not fix overlapping CIDR blocks.
D
Resize VNet-A to 10.0.0.0/15 so both VNets fit.
Why wrong: Making the larger range would actually expand overlap instead of removing it. Peering still cannot be established when address spaces overlap.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Change VNet-B to a non-overlapping address space, such as 10.1.0.0/24.
VNet peering requires that the address spaces of the two virtual networks do not overlap. If VNet-A uses 10.0.0.0/16 and VNet-B also uses 10.0.0.0/16, they conflict, preventing peering. Changing VNet-B to a non-overlapping address space like 10.1.0.0/24 resolves this conflict, allowing the peering to be established.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Change VNet-B to a non-overlapping address space, such as 10.1.0.0/24.
Why this is correct
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.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add a route table to VNet-B before creating the peering.
Why it's wrong here
Route tables do not resolve overlapping address spaces. The peering fails before any routing behavior matters.
When this WOULD be correct
In a scenario where VNet peering is established but traffic fails to route correctly between subnets, adding a route table with specific routes (e.g., to force traffic through a firewall or VPNgateway) would be the correct solution.
✗
Enable gateway transit on VNet-A.
Why it's wrong here
Gateway transit is used to share a VPN or ExpressRoute gateway through peering. It does not fix overlapping CIDR blocks.
When this WOULD be correct
In a scenario where VNet-A needs to provide a VPNgateway to VNet-B for hybrid connectivity, and VNet-B does not have its own gateway, enabling gateway transit on VNet-A would allow VNet-B to use VNet-A's gateway.
✗
Resize VNet-A to 10.0.0.0/15 so both VNets fit.
Why it's wrong here
Making the larger range would actually expand overlap instead of removing it. Peering still cannot be established when address spaces overlap.
When this WOULD be correct
This option would be correct if the question asked for a change to allow both VNets to communicate via a VPNgateway or to accommodate more resources within VNet-A without overlapping with VNet-B, but the address spaces must be non-overlapping for peering.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓Change VNet-B to a non-overlapping address space, such as 10.1.0.0/24.Correct answer▾
Why this is correct
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.
✗Add a route table to VNet-B before creating the peering.Wrong answer — click to see why▾
Why this is wrong here
Adding a route table to VNet-B does not resolve overlapping address spaces, which is the root cause preventing VNet peering. VNet peering requires non-overlapping address ranges; routing tables are irrelevant to this prerequisite.
★ When this WOULD be the correct answer
In a scenario where VNet peering is established but traffic fails to route correctly between subnets, adding a route table with specific routes (e.g., to force traffic through a firewall or VPN gateway) would be the correct solution.
Why candidates choose this
Candidates may confuse connectivity issues with routing problems, assuming that a route table can fix peering failures, or they may think that route tables are required for all peering setups.
✗Enable gateway transit on VNet-A.Wrong answer — click to see why▾
Why this is wrong here
Enabling gateway transit on VNet-A is unrelated to the address overlap issue. The peering fails because VNet-A (10.0.0.0/16) and VNet-B (10.0.0.0/24) have overlapping address spaces, which is not resolved by gateway transit.
★ When this WOULD be the correct answer
In a scenario where VNet-A needs to provide a VPN gateway to VNet-B for hybrid connectivity, and VNet-B does not have its own gateway, enabling gateway transit on VNet-A would allow VNet-B to use VNet-A's gateway.
Why candidates choose this
Candidates may confuse gateway transit as a general fix for peering issues, or think it helps with routing between overlapping VNets, not realizing address overlap is a fundamental constraint.
✗Resize VNet-A to 10.0.0.0/15 so both VNets fit.Wrong answer — click to see why▾
Why this is wrong here
Resizing VNet-A to 10.0.0.0/15 would still overlap with VNet-B's 10.0.0.0/16, as 10.0.0.0/15 includes 10.0.0.0/16. Overlapping address spaces prevent VNet peering from being established.
★ When this WOULD be the correct answer
This option would be correct if the question asked for a change to allow both VNets to communicate via a VPN gateway or to accommodate more resources within VNet-A without overlapping with VNet-B, but the address spaces must be non-overlapping for peering.
Why candidates choose this
Candidates may think that expanding VNet-A's address space will resolve the overlap by making both VNets fit, but they overlook that the expanded range still contains the original overlapping subnet.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse overlapping address spaces with routing issues, thinking that adding route tables or enabling gateway transit will fix the peering failure, when in fact the fundamental requirement is non-overlapping IP ranges.
Detailed technical explanation
How to think about this question
Azure VNet peering uses a hub-and-spoke or mesh topology where each VNet must have a unique, non-overlapping CIDR block. The peering connection is established at the Azure Resource Manager level, and the address spaces are validated during creation; if they overlap, the API returns a conflict error. In real-world scenarios, overlapping address spaces often occur when merging networks from different organizations or during migration, requiring careful IP address planning or use of NAT solutions.
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.
TExam Day Tips
→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.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
Visual reference
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Implement and Manage Virtual Networking — This question tests Implement and Manage Virtual Networking — Read the scenario before looking for a memorised answer..
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. — VNet peering requires that the address spaces of the two virtual networks do not overlap. If VNet-A uses 10.0.0.0/16 and VNet-B also uses 10.0.0.0/16, they conflict, preventing peering. Changing VNet-B to a non-overlapping address space like 10.1.0.0/24 resolves this conflict, allowing the peering to be established.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.