The answer is to set the spoke VNet’s custom DNS server to 10.50.0.4. This is correct because in a hub-spoke topology, cross-VNet DNS resolution requires spoke VMs to forward their name queries to a DNS server in the hub that is configured to resolve internal names; by default, Azure-provided DNS cannot resolve private hostnames across peered VNets. The hub’s DNS server at 10.50.0.4 acts as a central resolver, so pointing the spoke VNet’s custom DNS setting there ensures that queries for hub resources are properly answered. On the AZ-104 exam, this scenario tests your understanding of custom DNS configuration in VNet peering—a common trap is assuming Azure DNS automatically works across peered VNets, but it does not for private name resolution. Remember the tip: “Hub DNS, spoke forward” to recall that the spoke must forward to the hub’s custom DNS server for internal name resolution.
AZ-104 Implement and Manage Virtual Networking Practice Question
This AZ-104 practice question tests your understanding of implement and manage virtual networking. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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
Hub VNet:
- DNS server VM: 10.50.0.4
Spoke VNet:
- Default DNS setting: Azure-provided
Observed behavior:
- VM in spoke can ping hub VM by IP address
- nslookup app01.corp.local returns NXDOMAIN
Based on the exhibit, what configuration should the administrator change so VMs in the spoke can resolve internal names from the hub?
Hub VNet:
- DNS server VM: 10.50.0.4
Spoke VNet:
- Default DNS setting: Azure-provided
Observed behavior:
- VM in spoke can ping hub VM by IP address
- nslookup app01.corp.local returns NXDOMAIN
A
Add a route table entry that points to the hub DNS server.
Why wrong: Route tables direct packets, but they do not control name resolution for DNS queries.
B
Set the spoke VNet custom DNS server to 10.50.0.4.
The spoke is still using Azure-provided DNS, which cannot resolve the hub's internal records. Pointing the spoke VNet to the hub DNS server lets its VMs query the same internal namespace and resolve names correctly.
C
Enable a service endpoint for Microsoft.Storage on the spoke subnet.
Why wrong: Service endpoints help private access to supported Azure services, but they do not change DNS behavior for internal host names.
D
Create a private endpoint for the spoke VM subnet.
Why wrong: Private endpoints give a private IP to a PaaS service, not to normal VM-to-VM name resolution inside a hub network.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set the spoke VNet custom DNS server to 10.50.0.4.
The hub VNet has a DNS server at 10.50.0.4 that is configured to resolve internal names. By setting the spoke VNet's custom DNS server to 10.50.0.4, VMs in the spoke will forward DNS queries to that server, enabling resolution of internal names from the hub. This overrides the default Azure-provided DNS and directs name resolution to the hub's DNS infrastructure.
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 entry that points to the hub DNS server.
Why it's wrong here
Route tables direct packets, but they do not control name resolution for DNS queries.
✓
Set the spoke VNet custom DNS server to 10.50.0.4.
Why this is correct
The spoke is still using Azure-provided DNS, which cannot resolve the hub's internal records. Pointing the spoke VNet to the hub DNS server lets its VMs query the same internal namespace and resolve names correctly.
Related concept
Read the scenario before looking for a memorised answer.
✗
Enable a service endpoint for Microsoft.Storage on the spoke subnet.
Why it's wrong here
Service endpoints help private access to supported Azure services, but they do not change DNS behavior for internal host names.
✗
Create a private endpoint for the spoke VM subnet.
Why it's wrong here
Private endpoints give a private IP to a PaaS service, not to normal VM-to-VM name resolution inside a hub network.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is confusing network routing (route tables) with DNS resolution; candidates often think adding a route to the hub DNS server's IP will fix name resolution, but DNS queries are sent to the configured DNS server address, not routed based on destination IP.
Detailed technical explanation
How to think about this question
When you set a custom DNS server on a VNet, Azure assigns that server's IP address to all VMs via DHCP, overriding the default Azure DNS (168.63.129.16). The VMs then send all DNS queries to that custom server, which must be configured as a DNS forwarder or have appropriate zone records to resolve internal names. In hub-spoke topologies, the hub DNS server often hosts private DNS zones or forwards to on-premises DNS, making this configuration essential for cross-VNet name resolution.
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.
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: Set the spoke VNet custom DNS server to 10.50.0.4. — The hub VNet has a DNS server at 10.50.0.4 that is configured to resolve internal names. By setting the spoke VNet's custom DNS server to 10.50.0.4, VMs in the spoke will forward DNS queries to that server, enabling resolution of internal names from the hub. This overrides the default Azure-provided DNS and directs name resolution to the hub's DNS infrastructure.
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 →
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. Based on the exhibit, what should the administrator configure so the VM in the spoke VNet can resolve internal hostnames that are hosted on the DNS server in the hub VNet?
The team has already verified that IP connectivity between the spoke VM and the hub VM works.
hard
✓ A.Set the SpokeVNet DNS server list to use 10.40.0.4 so the spoke queries the hub resolver directly.
B.Create a private endpoint for web01.corp.contoso.local in the spoke VNet so DNS resolves automatically.
C.Enable gateway transit on the peering so the spoke inherits the hub VNet DNS configuration.
D.Add inbound and outbound NSG rules allowing UDP and TCP port 53 between the two VNets.
Why A: Option A is correct because setting the SpokeVNet DNS server list to 10.40.0.4 (the IP of the DNS server in the hub VNet) configures the spoke VNet to forward all DNS queries to that custom DNS server. Since IP connectivity between the VNets is already verified, the spoke VM can resolve internal hostnames hosted on the hub DNS server. This is the standard method for cross-VNet DNS resolution when using a custom DNS server in a hub-and-spoke topology.
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.