mediummultiple choiceObjective-mapped

A hub-and-spoke environment uses a DNS server VM in the hub VNet at 10.8.0.4 to resolve internal names such as app01.corp.local. The spoke VNet can reach hub VMs by IP after peering, but name resolution still fails from the spoke. What should the administrator configure so VMs in the spoke use the hub DNS server?

Question 1mediummultiple choice
Full question →

A hub-and-spoke environment uses a DNS server VM in the hub VNet at 10.8.0.4 to resolve internal names such as app01.corp.local. The spoke VNet can reach hub VMs by IP after peering, but name resolution still fails from the spoke. What should the administrator configure so VMs in the spoke use the hub DNS server?

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 an inbound NSG rule on the spoke subnet to allow UDP and TCP 53 to 10.8.0.4.

NSGs can allow or deny traffic, but they do not tell VMs which DNS server to query. The spoke still needs a DNS client configuration that points to the hub server.

B

Best answer

Configure the spoke VNet to use 10.8.0.4 as a custom DNS server.

A spoke VNet can inherit DNS behavior from a custom DNS setting on the VNet itself. Once the spoke VNet is configured to use 10.8.0.4, its VMs will send name-resolution queries to the hub DNS server over the peering connection. This is the right fix when direct IP connectivity works but internal names do not resolve.

C

Distractor review

Create a service endpoint for Microsoft.Storage on the spoke subnet.

Service endpoints extend subnet identity to supported Azure services, but they do not affect DNS server selection or internal name resolution across peered VNets.

D

Distractor review

Add a user-defined route for 10.8.0.4/32 pointing to the virtual network gateway.

A UDR changes packet forwarding, not DNS client settings. Sending traffic to the DNS server through a gateway is unnecessary when the VNet can already reach it.

Common exam trap

Common exam trap: usable hosts are not the same as total addresses

Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.

Technical deep dive

How to think about this question

Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.

KKey Concepts to Remember

  • CIDR notation defines the prefix length.
  • Block size helps identify subnet boundaries.
  • Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
  • The required host count determines the smallest suitable subnet.

TExam Day Tips

  • Write the block size before choosing the subnet.
  • Check whether the question asks for hosts, subnets or a specific address range.
  • Do not confuse /24, /25, /26 and /27 host counts.

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?

CIDR notation defines the prefix length.

What is the correct answer to this question?

The correct answer is: Configure the spoke VNet to use 10.8.0.4 as a custom DNS server. — When a hub VNet contains a DNS server VM and spoke VNets must resolve internal names through it, the spoke VNet must be configured to use that DNS server address. Peering only provides network reachability; it does not automatically change DNS behavior. After setting the custom DNS server on the spoke VNet, VMs there will query 10.8.0.4 for internal records such as app01.corp.local. Why others are wrong: NSG rules can permit DNS traffic, but they do not assign a DNS server to clients. Service endpoints are for Azure PaaS access and are unrelated to name resolution. A UDR can influence routing, but DNS queries still go wherever the client is configured to send them, so it will not fix the name-resolution 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.