Exam AZ-700 topic 2 question 30 discussion

NYN VM5 is in VNET3 and VNET3 isn't linked to the fabrikam.com private DNS zone. This means it won't be able to resolve anything in that private DNZ zone until it is linked.

NYN 10.4.0.2 and 10.4.0.5 are within same subnet that was initially not resolving

NYN N - No Link to VNET3 so another IP from VNET3 [10.4.0.2] has no impact. Y - Link to VNET3 resolves the issue N - No impact if there is no link to VNET3

This is NYN because the problem is that there is no link to VNET3

Appeared on Exam November - 2023

I vote NYN and reason below, i believe on option 1 and 3 we all agree N but 2 is question Mark First the DNS provide 168.63.129.16 is also know as internal.cloudapp.net which is the default Azure provided DNS and all vNETS have access to it by default So when you create V network link to vNET3 where vm resides this will enable vm5 to resolve any FQDN in the private DNS, however very important POINT, the default DNS is still can be used to resolve name that are not in the private DNS i.e. that are using the default Azure DNS - see link below https://learn.microsoft.com/en-us/azure/dns/dns-faq-private One important point, IF you statically configured the IP and DNS within the OS to another DNS server and you link the vNET where VM reside to Azure Private DNS than the statically assigned configurations take precedence and in this case vm5 will not resolve app1

NNN 1) How DNS address will resolve app1.fabricam.zom hostname if there is no connection between DNS zone and VNet3? 2) link to Vnet3 is not enogh because there is no DNS record to VM5, and conflicting DNS records app1.fabricam.com CNAME

No Yes No

n/y/n . There is no mention of 10.4.0.2 and what it is in the question.