- A
Add a route table to the spoke subnet pointing to the private endpoint IP.
Why wrong: Routing is not the problem because the VM already reaches the service by IP. Name resolution requires DNS configuration.
- B
Link the private DNS zone to the spoke VNet as well.
Private DNS zones must be linked to every VNet that needs to resolve the private endpoint name through Azure-provided DNS behavior. Since the spoke VNet is not linked to the zone, its VM does not receive the private endpoint record and cannot resolve the storage account FQDN correctly. Linking the zone to the spoke VNet allows name resolution to return the private IP.
- C
Enable gateway transit on the peering connection.
Why wrong: Gateway transit is for sharing a VPN or ExpressRoute gateway, not for distributing private DNS zone records.
- D
Create an NSG rule to allow DNS traffic to the storage account.
Why wrong: NSGs do not control DNS record creation, and the storage account is not the source of the DNS response.
AZ-104 Implement and Manage Virtual Networking Practice Question
This AZ-104 practice question tests your understanding of implement and manage virtual networking. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
Two VNets are peered successfully, and a VM in the spoke can reach a private endpoint in the hub by IP address. However, the VM cannot resolve the storage account name to the private endpoint FQDN. The private DNS zone is linked only to the hub VNet. What should the administrator do?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Link the private DNS zone to the spoke VNet as well.
The VM can reach the private endpoint by IP, confirming that network connectivity (peering and routing) is working. However, name resolution fails because the private DNS zone, which contains the private endpoint FQDN mapping, is linked only to the hub VNet. By linking the private DNS zone to the spoke VNet (option B), the spoke VMs will use Azure-provided DNS to resolve the storage account name to the private IP, enabling seamless name resolution across the peered VNets.
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.
- ✗
Add a route table to the spoke subnet pointing to the private endpoint IP.
Why it's wrong here
Routing is not the problem because the VM already reaches the service by IP. Name resolution requires DNS configuration.
When this WOULD be correct
A route table would be correct if the VM could not reach the private endpoint by IP due to asymmetric routing or missing routes, such as when the private endpoint is in a different VNet without proper peering or when using forced tunneling.
- ✓
Link the private DNS zone to the spoke VNet as well.
Why this is correct
Private DNS zones must be linked to every VNet that needs to resolve the private endpoint name through Azure-provided DNS behavior. Since the spoke VNet is not linked to the zone, its VM does not receive the private endpoint record and cannot resolve the storage account FQDN correctly. Linking the zone to the spoke VNet allows name resolution to return the private IP.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Enable gateway transit on the peering connection.
Why it's wrong here
Gateway transit is for sharing a VPN or ExpressRoute gateway, not for distributing private DNS zone records.
When this WOULD be correct
An administrator needs to enable connectivity from a spoke VNet to on-premises resources via the hub's VPN gateway. The hub has a VPN gateway configured, and the spoke VNet must use it to reach on-premises networks. Enabling 'Use remote gateways' on the spoke peering and 'Allow gateway transit' on the hub peering would be the correct solution.
- ✗
Create an NSG rule to allow DNS traffic to the storage account.
Why it's wrong here
NSGs do not control DNS record creation, and the storage account is not the source of the DNS response.
When this WOULD be correct
This option would be correct in a scenario where a VM cannot connect to a storage account via private endpoint because the NSG on the subnet is blocking outbound traffic to the private endpoint IP address on the required port (e.g., 443 for HTTPS). Adding an NSG rule to allow that traffic would resolve the connectivity issue.
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.
✓Link the private DNS zone to the spoke VNet as well.Correct answer▾
Why this is correct
Private DNS zones must be linked to every VNet that needs to resolve the private endpoint name through Azure-provided DNS behavior. Since the spoke VNet is not linked to the zone, its VM does not receive the private endpoint record and cannot resolve the storage account FQDN correctly. Linking the zone to the spoke VNet allows name resolution to return the private IP.
✗Add a route table to the spoke subnet pointing to the private endpoint IP.Wrong answer — click to see why▾
Why this is wrong here
The issue is DNS resolution, not routing. The VM can already reach the private endpoint by IP, so adding a route table does not help resolve the storage account name to the private endpoint FQDN.
★ When this WOULD be the correct answer
A route table would be correct if the VM could not reach the private endpoint by IP due to asymmetric routing or missing routes, such as when the private endpoint is in a different VNet without proper peering or when using forced tunneling.
Why candidates choose this
Candidates may confuse network connectivity issues with DNS resolution, assuming that if the VM cannot resolve the name, a route is needed to direct traffic to the private endpoint.
✗Enable gateway transit on the peering connection.Wrong answer — click to see why▾
Why this is wrong here
Gateway transit is used to allow a peered VNet to use the hub's VPN/ExpressRoute gateway for connectivity to on-premises networks, not for DNS resolution of private endpoints. The issue here is DNS resolution, not routing or gateway access.
★ When this WOULD be the correct answer
An administrator needs to enable connectivity from a spoke VNet to on-premises resources via the hub's VPN gateway. The hub has a VPN gateway configured, and the spoke VNet must use it to reach on-premises networks. Enabling 'Use remote gateways' on the spoke peering and 'Allow gateway transit' on the hub peering would be the correct solution.
Why candidates choose this
Candidates may confuse the need for routing traffic to the private endpoint with the need for DNS resolution, or mistakenly think that enabling gateway transit will also forward DNS queries to the hub's DNS servers.
✗Create an NSG rule to allow DNS traffic to the storage account.Wrong answer — click to see why▾
Why this is wrong here
The issue is DNS resolution, not network traffic. The VM can already reach the private endpoint by IP, so NSG rules for DNS traffic are irrelevant because DNS queries are sent to the Azure-provided DNS (168.63.129.16) or a custom DNS server, not to the storage account's IP.
★ When this WOULD be the correct answer
This option would be correct in a scenario where a VM cannot connect to a storage account via private endpoint because the NSG on the subnet is blocking outbound traffic to the private endpoint IP address on the required port (e.g., 443 for HTTPS). Adding an NSG rule to allow that traffic would resolve the connectivity issue.
Why candidates choose this
Candidates may think that DNS resolution failure is due to traffic being blocked by NSGs, confusing network connectivity issues with DNS resolution issues. They might assume that allowing DNS traffic to the storage account's IP would enable name resolution.
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 assume that VNet peering automatically extends DNS resolution for private endpoints, but in reality, each VNet must be explicitly linked to the private DNS zone for name resolution to work across the peering.
Detailed technical explanation
How to think about this question
Azure Private DNS zones use a split-horizon DNS mechanism where the zone is authoritative only within VNets that are linked to it. When a VM in the spoke VNet queries the storage account FQDN, Azure DNS checks if the spoke VNet is linked to the private zone; if not, it falls back to public DNS resolution, returning the public IP instead of the private endpoint IP. Linking the zone to the spoke VNet enables automatic registration and resolution of private endpoint FQDNs, leveraging the Azure DNS infrastructure without requiring custom DNS servers or conditional forwarders.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Visual reference
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Implement and Manage Virtual Networking — study guide chapter
Learn the concepts, then practise the questions
- →
Implement and Manage Virtual Networking practice questions
Targeted practice on this topic area only
- →
All AZ-104 questions
1,170 questions across all exam domains
- →
AZ-104 study guide
Full concept coverage aligned to exam objectives
- →
AZ-104 practice test guide
How to use practice tests most effectively before exam day
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.
Manage Azure Identities and Governance practice questions
Practise AZ-104 questions linked to Manage Azure Identities and Governance.
Implement and Manage Storage practice questions
Practise AZ-104 questions linked to Implement and Manage Storage.
Deploy and Manage Azure Compute practice questions
Practise AZ-104 questions linked to Deploy and Manage Azure Compute.
Implement and Manage Virtual Networking practice questions
Practise AZ-104 questions linked to Implement and Manage Virtual Networking.
Monitor and Maintain Azure Resources practice questions
Practise AZ-104 questions linked to Monitor and Maintain Azure Resources.
AZ-104 Azure RBAC practice questions
Practise AZ-104 questions linked to AZ-104 Azure RBAC.
AZ-104 storage account practice questions
Practise AZ-104 questions linked to AZ-104 storage account.
AZ-104 virtual network practice questions
Practise AZ-104 questions linked to AZ-104 virtual network.
AZ-104 NSG practice questions
Practise AZ-104 questions linked to AZ-104 NSG.
AZ-104 Azure Monitor practice questions
Practise AZ-104 questions linked to AZ-104 Azure Monitor.
AZ-104 backup practice questions
Practise AZ-104 questions linked to AZ-104 backup.
AZ-104 managed identity practice questions
Practise AZ-104 questions linked to AZ-104 managed identity.
Practice this exam
Start a free AZ-104 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-104 question test?
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: Link the private DNS zone to the spoke VNet as well. — The VM can reach the private endpoint by IP, confirming that network connectivity (peering and routing) is working. However, name resolution fails because the private DNS zone, which contains the private endpoint FQDN mapping, is linked only to the hub VNet. By linking the private DNS zone to the spoke VNet (option B), the spoke VMs will use Azure-provided DNS to resolve the storage account name to the private IP, enabling seamless name resolution across the peered VNets.
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 →
Keep practising
More AZ-104 practice questions
- A storage automation service principal must upload, read, and delete blob data in one container by using Microsoft Entra…
- A subnet contains several application servers. You need to allow inbound TCP 3389 only from a management subnet named Su…
- A subscription admin wants to investigate who changed a resource and also review the platform-generated events for that…
- Based on the exhibit, which Azure feature should the administrator use to track this kind of platform-wide service issue…
- An administrator wants a script running on an Azure VM to create a resource in Azure without storing any passwords or cl…
- A PowerShell script runs on an Azure VM every night and uses Azure CLI commands to create tags and VM resources in anoth…
Last reviewed: Jun 11, 2026
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.