HOTSPOT -
You have an Azure subscription named Subscription1. Subscription1 contains the resources in the following table.
In Azure, you create a private DNS zone named adatum.com. You set the registration virtual network to VNet2. The adatum.com zone is configured is shown in the following exhibit.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:
Box 1: No -
Azure DNS provides automatic registration of virtual machines from a single virtual network that's linked to a private zone as a registration virtual network. VM5 does not belong to the registration virtual network though.
Box 2: No -
Forward DNS resolution is supported across virtual networks that are linked to the private zone as resolution virtual networks. VM5 does belong to a resolution virtual network.
Box 3: Yes -
VM6 belongs to registration virtual network, and an A (Host) record exists for VM9 in the DNS zone.
By default, registration virtual networks also act as resolution virtual networks, in the sense that DNS resolution against the zone works from any of the virtual machines within the registration virtual network.
References:
https://docs.microsoft.com/en-us/azure/dns/private-dns-overview
No, No, Yes.
given answer is correct.
Answer is correct. DNS is registered in VNet1 and VNets are not peered. 1. No. It will not be registered, because VM5 is not in VNET2. 2. No. It will not resolve VM9, because VM5 is not in VNET2. 3. Yes. It will resolve VM9, because VM6 is in VNET2 and VM9 has an A record.
Answer is correct. DNS is registered in VNet1 and VNets are not peered. 1. No. It will not be registered, because VM5 is not in VNET1. 2. No. It will not resolve VM9, because VM5 is not in VNET1. 3. Yes. It will resolve VM9, because VM6 is in VNET1 and VM9 has an A record.
I think you confuse VNet1 and VNet2
N,N,Y The records contained in a private DNS zone aren't resolvable from the Internet. DNS resolution against a private DNS zone works only from virtual networks that are linked to it. You can link a private DNS zone to one or more virtual networks by creating virtual network links. You can also enable the autoregistration feature to automatically manage the life cycle of the DNS records for the virtual machines that get deployed in a virtual network.
How am I supposed to know which VNET(s) the zone links with?
The question says it.
Answer #2 should be Yes, with explanation given for positive answer.
i mean vnet_1 is not linked to the private dns zone.
vnet is not linked to the private dns zone. DNS forwarding needs a custom dns server deployed in the vnet which we don't have in this case.
i mean vnet_1 is not linked to the private dns zone.
no | yes | yes (*presuming autoregistration is enabled!?) if vnet2 (registration vnet) is 10.1.0.x and holds vms 1,6 and 9, then all 3 vms get DNS records created. only vnet1 does not get auto DNS records (vm5)
I think the question is a bit unclear because it mentions a "registration virtual network" for the DNS zone. That term does not exist in the documentation. There are "linked virtual networks" - which can resolve that DNS zone - and these "linked virtual networks" can be enabled for "automatic registration". The question implies that only VNet2 is linked and has "automatic registration" enabled, but it does not clearly state whether VNet1 is linked or not.
1. Azure DNS provides automatic registration of virtual machines from a single virtual network that's linked to a private zone as a registration virtual network. VM5 belongs to VNET1 that is not linked to the private zone. 2. Forward DNS resolution is supported across virtual networks that are linked to the private zone as resolution virtual networks. VM5 belongs to VNET1 that is not linked to the private zone. 3. VM6 belongs to registration virtual network, and an A (Host) record exists for VM9 in the DNS zone. No No Yes
YYN: VM5 connected to Vnet1
first of write, read the question please