Exam AZ-104 topic 5 question 80 discussion

Solution seems wrong. Should be No/Yes/No (not tested) No: Server2 uses Server1 for DNS. Server1 has no host2.contoso.com record for 131.107.50.50. It would work if VNET1 hat a virtual network link to the private zone contoso.com. Yes: Server2 uses Server1 for DNS. Server1 has a host1.contoso.com record for 131.107.10.15 No: Server3 uses 10.10.0.4 as DNS (inherited from VNET2). 10.10.0.4 (Server1) has no record for host2.contoso.com. The virtual network link for the private zone contoso.com on VNET2 won't be used since the DNS from VNET1 is set on VNET2. VNET1 DNS is not aware of the private zone contoso.com. It would work if VNET1 had a virtual network link to the private zone contoso.com.

I just tested this for myself, results were: server 2 resolve host2.contoso.com - NO - only host1 exists in the server1-hosted DNS zone, so cannot resolve - and setting server2 to use server1 as a DNS server means it does not use any other DNS servers. server 2 resolve host1.contoso.com - YES to the server1 hosted DNS address ie. 131.107.10.15 server3 resolve host2.contoso.com - YES to the Azure hosted DNS address ie. 131.107.50.50. server3 can also resolve host1.contoso.com to the Azure hosted DNS address (of course). hope this helps :)

Server2 resolves host2.contoso.com to 131.107.50.50. Server2 is in VNET1, which uses the Azure-provided DNS server by default, as its DNS configuration is inherited from the virtual network. The Azure-provided DNS server does not have knowledge of the private DNS zone contoso.com, which is linked to VNET2. Therefore, Server2 will not be able to resolve host2.contoso.com to 131.107.50.50, as that record is only available in the Azure private DNS zone linked to VNET2. Answer: No Server2 resolves host1.contoso.com to 131.107.10.15. Similar to the previous case, Server2 is in VNET1 and relies on the Azure-provided DNS server. The record for host1.contoso.com exists in the DNS server hosted by Server1, which is also in VNET1. Since Server1 is configured as a DNS server for the contoso.com zone, Server2 can resolve host1.contoso.com to 131.107.10.15. Answer: Yes

NYY Server2 resolves host2.contoso.com to 131.107.50.50 No: Server2 is in VNET1, and its DNS server inherits from the virtual network. It does not have direct access to the private DNS zone, which is linked to VNET2. Therefore, it cannot resolve this record. Server2 resolves host1.contoso.com to 131.107.10.15 Yes: Server2 can resolve host1.contoso.com since it’s a public DNS zone and accessible through the Azure-provided DNS. Server3 resolves host2.contoso.com to 131.107.50.50 Yes: Server3 is in VNET2, which has a virtual network link to the private DNS zone. Thus, it can resolve host2.contoso.com.

WRONG No Yes No

No Yes Yes

Answer is YNY: Private DNS zones linked to a VNet are queried first when using the default DNS settings of a VNet. Azure provided DNS servers are queried next. However, if a custom DNS server is defined in a VNet, then private DNS zones linked to that VNet are not automatically queried, because the custom settings override the name resolution order. https://learn.microsoft.com/en-us/azure/dns/private-dns-privatednszone#private-dns-zone-resolution

Chat GPT can answer you better than here. Server2 resolves host2.contoso.com to 131.107.50.50. is YES Server2 does not resolve host1.contoso.com to 131.107.10.15. The correct answer is YES. Server2 does resolve host1.contoso.com to 131.107.10.15. Server3 resolves host2.contoso.com to 131.107.50.50. is YES

DNS in Peered VNets Independent DNS Configuration: Each VNet in Azure can be configured with its own DNS servers. When you peer VNets, these configurations remain independent. A VNet does not inherit or override the DNS server settings of the VNet it is peered with. Resolution Across Peered VNets: Resources in peered VNets can resolve DNS names as per their respective VNet’s DNS settings. If a resource in VNet A needs to resolve a name managed by a DNS server in VNet B, it can do so if the DNS server in VNet B is accessible and if the necessary DNS forwarding or conditional forwarding is set up. Custom DNS Scenarios: In scenarios where you have custom DNS servers, you might need to configure DNS forwarding or conditional forwarding to ensure proper name resolution across peered VNets. Azure-Provided DNS: If you are using Azure-provided DNS, the resolution of names for resources in Azure (like VMs) works across peered VNets without additional configuration.

what a shit design. just fire the engineer and fix this question.

Server 2 connects Server 1 DNS. 1. No - No entry for host2 2. Yes - host1 found 131.10710.15 Server 3 used VNET2 3. Yes - host2 found as 131.107.50.50 So resolved

In the exam today, 18/08/2023. First question was different, it was Server1

what the hell? every second question has confusion. Why are we not able to get the exact answers even after paying huge amount?

Server 2 => NIC2 => 10.10.0.4 => host2.contoso.com => No entry => No Server 2 => NIC2 => 10.10.0.4 => host1.contoso.com => 131.107.10.15 => Yes Server 3 => NIC3 => VNET2 => 10.10.0.4 => host2.contoso.com => No entry => No

N Y N is correct!

I do not understand how answers provided in the site can have so many incorrect answers. Exam topics needs to do better.

Agree with N,Y,Y. Comment from hanyahmed makes the most sense. For box3 see: https://learn.microsoft.com/en-us/azure/dns/private-dns-virtual-network-links "After you create a private DNS zone in Azure, you'll need to link a virtual network to it. Once linked, VMs hosted in that virtual network can access the private DNS zone. Every private DNS zone has a collection of virtual network link child resources. Each one of these resources represents a connection to a virtual network. A virtual network can be linked to private DNS zone as a registration or as a resolution virtual network."