Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft Certified: Azure Network Engineer Associate · Microsoft
Step Sequence / Reordering Question
Add and arrange the steps in the correct execution order.
Hotspot Solution:
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 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
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
1️⃣ NO → Changing VM5’s DNS server won’t help because VNet3 (where VM5 is located) isn’t linked to the private DNS zone. 2️⃣ YES → Linking VNet3 to the fabrikam.com private DNS zone will allow VM5 to resolve app1.fabrikam.com. 3️⃣ NO → Adding an A record won’t fix the issue since the problem is DNS zone access, not missing records.
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