VMs across several VNets must resolve a private zone name (e.g., db.corp.internal) to private IPs automatically. What's needed?
A.A public Azure DNS zone
Public zones serve internet-facing names — not VNet-internal resolution.
B.A Private DNS zone linked to each VNet with autoregistration
Private DNS zone + VNet links. Correct.
C.Azure-provided DNS (168.63.129.16) does this by default
The platform resolver handles Azure names, not custom private zones.
D.A custom DNS VM in each VNet
Custom DNS VMs are a workaround — Private DNS is the native service.
Why this answer
Azure Private DNS zones provide internal name resolution — link the zone to VNets (resolution works only from linked VNets) and enable autoregistration to create records automatically for VMs. Public zones resolve internet names; 168.63.129.16 is the platform resolver, not a zone host.
Correct answer: B · Last reviewed 2026-02-14
Official AWS references
Practice this interactively
Answer without seeing the solution first in the Virtual Networking practice session.
Practice Virtual Networking