Examkin

Soru

Zorluk: Çok zorConfigure Azure DNS Private and Public Zones

An enterprise Azure environment is configured with three virtual networks in the East US region: VNet-Hub, VNet-Prod, and VNet-Dev. VNet-Hub is peered directly with both VNet-Prod and VNet-Dev using default peering configurations. No peering exists between VNet-Prod and VNet-Dev. An administrator creates a Private DNS zone named internal.contoso.com and configures the following:

- A virtual network link from VNet-Hub to internal.contoso.com with auto-registration enabled.
- A virtual network link from VNet-Prod to internal.contoso.com with auto-registration disabled.
- No virtual network links are created for VNet-Dev.

Virtual machines VM-Hub, VM-Prod, and VM-Dev are deployed into their respective virtual networks, all configured to use the default Azure-provided DNS service. Which virtual machines will be able to resolve the name vm-hub.internal.contoso.com, and which virtual machines will have their DNS records automatically created in the private DNS zone?

  1. A
    Only VM-Hub can resolve the name; only VM-Hub has an auto-registered record.
  2. B
    VM-Hub, VM-Prod, and VM-Dev can resolve the name; VM-Hub and VM-Prod both have auto-registered records.
  3. VM-Hub and VM-Prod can resolve the name; only VM-Hub has an auto-registered record.Cevap
  4. D
    VM-Hub and VM-Prod can resolve the name; VM-Hub and VM-Prod both have auto-registered records.

Cevap

VM-Hub and VM-Prod can resolve the name; only VM-Hub has an auto-registered record.
To resolve records in an Azure Private DNS zone, a virtual network must be linked to that zone. Because VNet-Hub and VNet-Prod are linked, both VM-Hub and VM-Prod can resolve names in internal.contoso.com. VNet-Dev is not linked, and DNS resolution does not transit across virtual network peering connections, so VM-Dev cannot resolve the names. Auto-registration is only enabled on the link for VNet-Hub, which means only VM-Hub's hostname is registered automatically. VM-Prod's network link has auto-registration disabled, preventing its hostname from being registered.

Adım Adım Çözüm

1
Determine which virtual networks have active links to the Private DNS zone.
VNet-Hub and VNet-Prod are linked; VNet-Dev is not linked.
A virtual network link is required for VMs within a virtual network to resolve DNS queries against an Azure Private DNS zone.
2
Evaluate the transitiveness of Azure-provided DNS over peered networks.
VM-Dev cannot resolve internal.contoso.com names.
VNet peering does not provide transitive DNS resolution capability for Azure-provided DNS. Because VNet-Dev lacks a direct link to the zone, its VMs cannot query the zone.
3
Identify which links have auto-registration enabled.
VNet-Hub has auto-registration enabled; VNet-Prod has auto-registration disabled.
Auto-registration dictates whether the hostname of virtual machines in the linked network are automatically registered as A records in the private zone.
4
Combine resolution capabilities and registration status for the final state.
VM-Hub auto-registers and resolves; VM-Prod resolves but does not auto-register; VM-Dev neither registers nor resolves.
This matches the specific link configurations and registration states applied to each network link.

Anahtar Kavram

Azure Private DNS Zone Linking and Auto-Registration behavior across peered Virtual Networks
Bu soruyu puanla

Konular

Configure Azure DNS Private and Public Zones

Bu konudan daha fazla soru