networkSingle choice
You have a hub-and-spoke topology. HubVnet and SpokeVnet are peered. A private DNS zone named corp.internal is linked to HubVnet only. Virtual machines in SpokeVnet cannot resolve app1.corp.internal. You need to ensure that the VMs in SpokeVnet can resolve records in corp.internal. What should you do?
عندك Hub-and-spoke topology، والـ HubVnet والـ SpokeVnet متوصلين ببعض بـ Peering. فيه Private DNS zone اسمها corp.internal متوصلة بـ HubVnet بس. الـ VMs اللي في SpokeVnet مش قادرة تحل app1.corp.internal. محتاج تخلي الـ VMs اللي في SpokeVnet تقدر تحل الـ Records اللي في corp.internal. تعمل إيه؟
- ACreate a virtual network link between corp.internal and SpokeVnet.
- BEnable auto-registration on the existing HubVnet link.
- CEnable "Allow forwarded traffic" on the peering.
- DCreate a public DNS zone named corp.internal.
Why: A private DNS zone answers queries only from virtual networks that are linked to it. Peering connects the networks for traffic but does not share private DNS resolution, so SpokeVnet needs its own virtual network link (registration can stay disabled). Enabling auto-registration on the HubVnet link only makes hub VMs register their own records. "Allow forwarded traffic" affects routed traffic, not name resolution. A public zone would be resolvable from the internet and is the wrong scope for an internal namespace.
Exam skills it covers
- Configure Azure DNS