Examkin

Soru

Zorluk: ZorConfigure Azure DNS Private and Public Zones

You manage an Azure subscription that contains a private DNS zone named private.contoso.local and three virtual networks named VNet-East, VNet-West, and VNet-Central. Currently, VNet-East has a virtual network link to private.contoso.local with auto-registration enabled. You receive a new requirement to configure the networks to meet the following criteria:
- Virtual machines in VNet-West must be able to resolve names in private.contoso.local and must have their DNS records automatically registered in the zone.
- Virtual machines in VNet-Central must be able to resolve names in private.contoso.local but must not have their DNS records automatically registered.
- Virtual machines in VNet-East must still be able to resolve names in private.contoso.local, but automatic registration of their DNS records is no longer required.

Which administrative action should you perform?

  1. A
    Create a virtual network link from private.contoso.local to VNet-West with auto-registration enabled, and create a virtual network link from private.contoso.local to VNet-Central with auto-registration disabled.
  2. B
    Configure virtual network peering between VNet-East and VNet-West, and create a virtual network link from private.contoso.local to VNet-Central with auto-registration disabled.
  3. Disable auto-registration on the virtual network link for VNet-East, create a virtual network link for VNet-West with auto-registration enabled, and create a virtual network link for VNet-Central with auto-registration disabled.Cevap
  4. D
    Configure virtual network peering between VNet-East and VNet-West, and configure virtual network peering between VNet-East and VNet-Central.

Cevap

Disable auto-registration on the virtual network link for VNet-East, create a virtual network link for VNet-West with auto-registration enabled, and create a virtual network link for VNet-Central with auto-registration disabled.
The correct action is to disable auto-registration on the virtual network link for VNet-East, create a virtual network link for VNet-West with auto-registration enabled, and create a virtual network link for VNet-Central with auto-registration disabled. This configuration respects the limit of one auto-registration link per private DNS zone, while ensuring all three networks maintain name resolution access via their individual virtual network links.

Adım Adım Çözüm

1
Modify the existing virtual network link for VNet-East to disable auto-registration.
VNet-East remains linked to private.contoso.local for name resolution, but the auto-registration slot for the private DNS zone is freed up.
An Azure Private DNS zone enforces a strict limit of exactly one virtual network link with auto-registration enabled at any given time.
2
Create a new virtual network link between private.contoso.local and VNet-West, enabling the auto-registration setting.
VMs in VNet-West can resolve names in the private DNS zone, and their DNS records are automatically created in the zone.
This satisfies the requirement for VNet-West to have both name resolution and automatic record registration.
3
Create a new virtual network link between private.contoso.local and VNet-Central, leaving the auto-registration setting disabled.
VMs in VNet-Central can resolve names in the private DNS zone, but their records are not automatically registered.
This satisfies the resolution-only requirement for VNet-Central while staying within Azure limits.

Anahtar Kavram

Azure Private DNS Zone Virtual Network Links and Auto-Registration Limits
Tahmini Süre:2m 30s
Bu soruyu puanla

Konular

Configure Azure DNS Private and Public Zones

Bu konudan daha fazla soru