Examkin

Question

Difficulty: MediumConfigure Virtual Network Peering

Your company has an Azure environment containing two virtual networks in the East US region:
* `VNet-Prod` (10.80.0.0/1610.80.0.0/16) contains a virtual machine named `VM-Prod` and is linked to an Azure Private DNS zone named `private.contoso.com`.
* `VNet-Dev` (10.90.0.0/1610.90.0.0/16) contains a virtual machine named `VM-Dev`.

You establish a virtual network peering between `VNet-Prod` and `VNet-Dev` with the following configuration:
* 'Allow forwarded traffic' is enabled on both peering links.
* 'Allow gateway transit' is disabled on `VNet-Prod`.
* 'Use remote gateways' is disabled on `VNet-Dev`.

`VM-Dev` can successfully access `VM-Prod` using its private IP address, but it cannot resolve the name `vm-prod.private.contoso.com`.

Which action should you take to resolve the name resolution issue?

  1. Link VNet-Dev to the private.contoso.com Private DNS zone.Answer
  2. B
    Enable 'Allow gateway transit' on the peering link from VNet-Prod to VNet-Dev.
  3. C
    Enable 'Use remote gateways' on the peering link from VNet-Dev to VNet-Prod.
  4. D
    Enable DNS active registration for VNet-Dev in the private.contoso.com settings.

Answer

Link VNet-Dev to the private.contoso.com Private DNS zone.
Linking the development virtual network to the Private DNS zone allows the Azure DNS resolver in the development network to query the zone records. Peering only configures network routing; it does not share private DNS zone resolution spaces automatically.

Step-by-Step Solution

1
Verify the status of IP-level connectivity between the virtual networks.
IP connectivity is established via peering, but DNS resolution fails because peering does not transitively extend Private DNS zone resolution scope.
Ensures that the problem is not a lower-level network routing issue.
2
Check the virtual network links associated with the private.contoso.com Private DNS zone.
Identify that only VNet-Prod has an active virtual network link to the Private DNS zone.
For any virtual network to resolve names in an Azure Private DNS zone, it must be explicitly linked to that zone.
3
Add a new virtual network link in the Private DNS zone settings targeting VNet-Dev.
Azure-provided DNS in VNet-Dev can now query the DNS database of the Private DNS zone.
This establishes the logical control plane relationship required for name resolution.

Key Concept

Azure Private DNS Zone Virtual Network Links
Estimated Time:1m 30s
Rate this question

Topics

Configure Virtual Network Peering

More questions from this topic