Your company has an Azure subscription containing an Azure Private DNS zone named corp.contoso.com. You have two virtual networks named VNet1 and VNet2 in the same Azure region. You need to configure Azure Private DNS so that virtual machines in VNet1 can resolve names in corp.contoso.com and automatically register their own DNS records. Virtual machines in VNet2 must be able to resolve names in corp.contoso.com but must not automatically register their DNS records. Which two configurations should you implement? (Select two.)
- A virtual network link from corp.contoso.com to VNet1 with auto-registration enabledAnswer
- A virtual network link from corp.contoso.com to VNet2 with auto-registration disabledAnswer
- CA virtual network link from corp.contoso.com to VNet2 with auto-registration enabled
- DA virtual network peering connection between VNet1 and VNet2 with transit enabled
Answer
Configure a virtual network link from the private DNS zone to VNet1 with auto-registration enabled, and configure a virtual network link from the private DNS zone to VNet2 with auto-registration disabled.
To enable name resolution and auto-registration for VNet1, you must create a virtual network link from the Private DNS zone to VNet1 with auto-registration enabled. To allow only name resolution for VNet2 without auto-registration, you must link the Private DNS zone to VNet2 with auto-registration disabled. Azure Private DNS allows multiple virtual network links to a single zone, but only one link can have auto-registration enabled at any time.
Step-by-Step Solution
Key Concept
Azure Private DNS virtual network links and auto-registration behavior
Estimated Time:2m 0s