You have an Azure subscription that contains a Private DNS zone named `internal.contoso.com`. You have three virtual networks named `VNet-Admin`, `VNet-App`, and `VNet-DB` in the same region.
The resources are configured as follows:
- `VNet-Admin` is linked to `internal.contoso.com` with auto-registration enabled.
- `VNet-App` is linked to `internal.contoso.com` with auto-registration disabled.
- `VNet-DB` is not linked to `internal.contoso.com`.
- `VNet-App` and `VNet-DB` are connected via virtual network peering.
Which two statements accurately describe the DNS resolution and registration behavior in this subscription? (Select two.)
- Virtual machines in VNet-App can resolve the DNS records of virtual machines in VNet-Admin.Cevap
- Virtual machines in VNet-DB cannot resolve DNS records in internal.contoso.com.Cevap
- CVirtual machines in VNet-DB can resolve DNS records in internal.contoso.com because of the peering link with VNet-App.
- DVirtual machines in VNet-App automatically register their hostnames in internal.contoso.com.
Cevap
Virtual machines in VNet-App can resolve the DNS records of virtual machines in VNet-Admin, and virtual machines in VNet-DB cannot resolve DNS records in internal.contoso.com.
Virtual machines in virtual networks linked to an Azure Private DNS zone can resolve records within that zone. Because VNet-Admin is linked with auto-registration enabled, its VMs are registered. Because VNet-App is linked to the zone, its VMs can resolve those registered records. Since VNet-DB is not linked to the zone, it cannot resolve records within it. Virtual network peering does not transitively share Private DNS zone links, meaning VNet-DB remains unable to resolve internal names despite the peering link.
Adım Adım Çözüm
Anahtar Kavram
Azure Private DNS Zone virtual network links and auto-registration behavior
Tahmini Süre:1m 30s