mediummultiple choiceObjective-mapped

A company has a hub virtual network with a DNS server VM at 10.50.0.4 that hosts internal names such as app01.corp.local. A spoke virtual network is already peered to the hub. VMs in the spoke can reach resources in the hub by IP address, but they cannot resolve the internal host names. The company wants to keep DNS centralized and avoid deploying another DNS server in the spoke. What should the administrator configure?

Question 1mediummultiple choice
Full question →

A company has a hub virtual network with a DNS server VM at 10.50.0.4 that hosts internal names such as app01.corp.local. A spoke virtual network is already peered to the hub. VMs in the spoke can reach resources in the hub by IP address, but they cannot resolve the internal host names. The company wants to keep DNS centralized and avoid deploying another DNS server in the spoke. What should the administrator configure?

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

Create a private DNS zone for corp.local and link it only to the spoke subnet.

Private DNS zones are useful for Azure private endpoints, but they do not automatically use your existing custom DNS server for all internal records.

B

Best answer

Set the spoke virtual network to use 10.50.0.4 as a custom DNS server.

Configuring the spoke VNet with the hub DNS server IP sends name-resolution requests to the centralized server. Because VNet peering already provides network connectivity, the spoke can query 10.50.0.4 directly for internal names without deploying a second DNS server.

C

Distractor review

Add a user-defined route in the spoke to send DNS traffic to the hub VNet.

Routes control next hop selection for packets, but they do not replace DNS client configuration or determine which resolver a VM uses.

D

Distractor review

Enable gateway transit on the peering and set use remote gateways on the spoke.

Gateway transit is for using a VPN or ExpressRoute gateway across peered VNets, not for fixing ordinary name resolution between VNets.

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: Set the spoke virtual network to use 10.50.0.4 as a custom DNS server. — The spoke VNet must be configured to use the centralized DNS server at 10.50.0.4. VNet peering allows the spoke VM to reach the DNS server by private IP, but Azure does not automatically inherit custom DNS settings across peering. Once the spoke VNet points to that resolver, internal names such as app01.corp.local can be resolved without adding new DNS infrastructure in the spoke. Why others are wrong: A is a common mix-up with Azure Private DNS zones, but that feature is mainly for Azure private endpoint name resolution. C confuses routing with DNS configuration; routes do not select the resolver a VM queries. D is about sharing a gateway for hybrid connectivity, which does not address internal DNS resolution between peered VNets.

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.