easymultiple choiceObjective-mapped

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?

Question 1easymultiple choice
Full question →

Based on the exhibit, what configuration should the administrator change so VMs in the spoke can resolve internal names from the hub?

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 a route table entry that points to the hub DNS server.

Route tables direct packets, but they do not control name resolution for DNS queries.

B

Best answer

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

Distractor review

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

Service endpoints help private access to supported Azure services, but they do not change DNS behavior for internal host names.

D

Distractor review

Create a private endpoint for the spoke VM subnet.

Private endpoints give a private IP to a PaaS service, not to normal VM-to-VM name resolution inside a hub network.

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 VNet custom DNS server to 10.50.0.4. — Because the spoke VNet is still using Azure-provided DNS, it has no way to resolve the internal hostnames hosted on the hub DNS server. Setting the spoke VNet’s custom DNS server to 10.50.0.4 makes the spoke VMs send queries to the hub resolver. That is the correct fix for internal name resolution in this design. Why others are wrong: A route table cannot fix DNS. Service endpoints are unrelated to name resolution. A private endpoint is for Azure PaaS services, not for pointing VM clients at an internal DNS server. The issue shown is DNS configuration, not connectivity.

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.