Question 941 of 1,170
Implement and Manage Virtual NetworkingmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to add a virtual network link from the private DNS zone to AppVNet. This is required because a private DNS zone is scoped only to the VNets it is explicitly linked to, and VNet peering does not automatically propagate DNS resolution—it only provides IP connectivity. Even though the VMs in AppVNet can reach the private endpoint by IP across the peering, they cannot resolve the storage FQDN because the DNS zone is not accessible from AppVNet. On the AZ-104 exam, this scenario tests your understanding of how private DNS zones integrate with VNet peering and private endpoints; a common trap is assuming peering alone enables name resolution. Remember: peering handles the route, but the link handles the lookup. A helpful memory tip is “Link to think”—if you want a peered VNet to resolve a private endpoint’s FQDN, you must link the private DNS zone to that VNet.

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. AppVNet contains VMs that access a private endpoint in DataVNet successfully by IP, but name resolution fails for the storage FQDN. The private DNS zone is linked only to DataVNet. What should you do?

Question 1mediummultiple choice
Read the full DNS explanation →

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

Add a virtual network link from the private DNS zone to AppVNet.

The private DNS zone is linked only to DataVNet, so VMs in AppVNet cannot resolve the storage FQDN even though IP connectivity works via the VNet peering. By adding a virtual network link from the private DNS zone to AppVNet, you enable DNS resolution for the private endpoint's FQDN across the peered VNet. This is required because private DNS zones are scoped to the VNets they are linked to, and peering alone does not propagate DNS resolution.

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.

  • Create another peering connection from AppVNet to DataVNet.

    Why it's wrong here

    Peering already exists, and peering does not automatically extend private DNS zone visibility across VNets.

  • Add a virtual network link from the private DNS zone to AppVNet.

    Why this is correct

    Private endpoint name resolution depends on the private DNS zone being linked to the VNet where the clients reside. Because AppVNet is not linked to the zone, its VMs cannot resolve the private endpoint FQDN even though IP connectivity exists. Adding a virtual network link from the private DNS zone to AppVNet makes the private records available to those clients.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Create a public DNS zone with the same name as the private zone.

    Why it's wrong here

    A public DNS zone does not provide private endpoint resolution and can create conflicting records instead of fixing the lookup problem.

  • Assign a public IP address to the private endpoint.

    Why it's wrong here

    Private endpoints are intended to use private addresses. Adding a public IP defeats the purpose and does not solve the DNS zone linkage issue.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume VNet peering automatically extends DNS resolution for private endpoints, but peering only provides IP connectivity—DNS resolution requires explicit virtual network links to the private DNS zone.

Detailed technical explanation

How to think about this question

Private DNS zones use Azure DNS to resolve private endpoint FQDNs to private IP addresses, and they must be linked to each VNet that needs resolution. The virtual network link registers the VNet with the zone, enabling conditional forwarding of queries for that zone to Azure DNS. In a real-world scenario, if you have hub-spoke topologies, you would link the private DNS zone to the hub VNet and configure the spoke VNets to use the hub as a custom DNS server, or link the zone directly to each spoke for simplicity.

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.

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.

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.

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: Add a virtual network link from the private DNS zone to AppVNet. — The private DNS zone is linked only to DataVNet, so VMs in AppVNet cannot resolve the storage FQDN even though IP connectivity works via the VNet peering. By adding a virtual network link from the private DNS zone to AppVNet, you enable DNS resolution for the private endpoint's FQDN across the peered VNet. This is required because private DNS zones are scoped to the VNets they are linked to, and peering alone does not propagate DNS resolution.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on AZ-104

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A storage account is accessed from a VM in VNet A through a private endpoint. A VM in peered VNet B can connect to the storage account by IP, but when it uses the storage account name, it resolves to the public endpoint. What should the administrator configure?

medium
  • A.Enable a service endpoint on VNet B for Microsoft.Storage.
  • B.Link the private DNS zone for the storage account to VNet B.
  • C.Assign the VM in VNet B a managed identity.
  • D.Create a route table that points storage traffic to the private endpoint subnet.

Why B: The VM in VNet B can reach the storage account by IP because the private endpoint is accessible over the VNet peering, but DNS resolution still returns the public IP because the private DNS zone (privatelink.blob.core.windows.net) is not linked to VNet B. By linking the private DNS zone to VNet B, the VM will resolve the storage account name to the private endpoint IP, ensuring connectivity over the Microsoft backbone instead of the public internet.

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.