Exam AZ-104 topic 5 question 71 discussion

https://docs.microsoft.com/en-us/azure/dns/private-dns-virtual-network-links A virtual network can be linked to private DNS zone as a registration or as a resolution virtual network. Registration virtual network: A private DNS zone can have multiple registration virtual networks. However, every virtual network can only have one registration zone associated with it. Resolution virtual network: One private DNS zone can have multiple resolution virtual networks and a virtual network can have multiple resolution zones associated to it. 1. Yes No registration zone for VNET2. 2. Yes A virtual network can have multiple resolution zones associated to it. 3.Yes No registration zone for VNET2.

1. Yes 2. Yes. You can link VNET1 to Zone3.com A private DNS zone can have multiple registration virtual networks. However, every virtual network can only have one registration zone associated with it. 3. No. Auto registration is already enabled on Zone 1. When you add a link from VNET2 to Zone

Yes - because no auto registration exists for Link2 No - VNet and Zone are not in the same region No - Link1 already has an auto registration and you cannot have more than one.

WRONG Yes Yes Yes

just now tested in Lab, Y-Y-and No.. last box is No: because, getting an Error: A virtual network can only be linked to 1 Private DNS zone(s) with auto-registration enabled; in this case here already Vnet1 is enable in link1 under zone1.com

Y, Y, N Read the fourth bullet point in below article. https://learn.microsoft.com/en-us/azure/dns/private-dns-autoregistration#restrictions

Yes Yes Yes

I have to waste my 30 min to setup the resorces to try this one out....and here is what i got, 1. Yes - We can enable auto register provided there is no conflict 2. Yes - There is no impact of location on setting up Vnet link but in case v-net is already registered with another private zone then auto registration can't be enabled. 3. No, above reason.

Tested in Lab, correct answer is Yes, Yes, and for the 3rd box NO because if you try to create the link with enable auto registration it will error out and it will actually tell you that a virtual network can only be linked to one private DNS zone with auto-registration enabled. Do not waste much time on this, this is the correct answer.

Y - Y - Y. I tested this myself in a real environment. best to test it vs. making comments here without any test. 1. Y. You can click the checkbox to Enable Auto-Reg. Note: You can do this to any VNET as long as that VNET is not linked to another Zone with Auto-reg ON. So if VNET is in another zone but Auto-reg is OFF, then you can enable Auto-Reg in Only One Zone 2. Y. You can add Vnet1 to Zone3 but make sure Auto Reg is OFF. You cannot add Vnet1 to Zone3 with Auto Reg is ON. 3. Y. You can add Vnet2 to Zone1 and set to Auto Reg ON because VNET2 has no link yet to any zone with Auto Reg ON. to summarize: Zones can have multiple VNETs. Each VNET can be set to Auto Reg ON VNETs can be linked to multiple Zones but they can only Auto Reg to one Zone

I tested it in my LAB an here are results: 1. YES - you can enable auto registration for link2 2. YES - you can add virtual network link VNET1 to zone3 3. Yes - you can add virtual network link VNET2 to zone1.

what the hell? every second question has confusion. Why are we not able to get the exact answers even after paying a huge amount? whom should we follow? Discussion or Examtopic?

Y Y NO is correct!

Yes. Auto-registration can be enabled for Link2 because VNET2 is not currently a registration virtual network for any other private DNS zone. So it can become the registration virtual network for Zone2.com if auto-registration is enabled for Link2. Yes. You can create a link between VNET1 and Zone3.com. However, because VNET1 is already a registration virtual network for Zone1.com, you cannot enable auto-registration for this new link. This is because "every virtual network can only have one registration zone associated with it." No. You cannot enable auto-registration for this potential new link between VNET2 and Zone1.com because, as per the provided explanation, "every virtual network can only have one registration zone associated with it." Since VNET2 has already been linked to Zone2.com with auto-registration enabled (as per answer 1), it cannot become the registration virtual network for Zone1.com as well. https://learn.microsoft.com/en-us/azure/dns/private-dns-virtual-network-links#registration-virtual-network

Agree with Y,N,N Q1: Y. Looks like it needs to be done when the link is created, and doesn't specify it it can be retroactively enabled, but yes can be done. https://learn.microsoft.com/en-us/azure/dns/private-dns-autoregistration Q2 + Q3, N. Already linked. "From the virtual network perspective, private DNS zone becomes the registration zone for that virtual network. A private DNS zone can have multiple registration virtual networks. However, every virtual network can only have one registration zone associated with it" https://learn.microsoft.com/en-us/azure/dns/private-dns-virtual-network-links

Answer will be yes for 3. When auto-registration is not enabled while linking its called resolution means VNET is not registered with DNS and it using for resolution and one VNET can have multiple resolution . refer this for detailed info - https://learn.microsoft.com/en-us/azure/dns/private-dns-virtual-network-links

Y Y N is the correct answer guys