You have the Azure virtual networks shown in the following table.

To which virtual networks can you establish a peering connection from VNet1?
You have the Azure virtual networks shown in the following table.
To which virtual networks can you establish a peering connection from VNet1?
You cannot establish a peering connection between virtual networks that have overlapping address spaces. VNet1 (10.11.0.0/16) and VNet2 (10.11.0.0/17) have overlapping address spaces, so they cannot be peered. VNet3 (10.10.0.0/22) and VNet4 (192.168.16.0/22) do not have overlapping address spaces with VNet1 and can be peered with VNet1. Therefore, the correct answer is that you can establish a peering connection from VNet1 to VNet3 and VNet4 only.
C. VNet3 and VNet4 only
Vnet1 and Vnet2 IPs are overlapping.
no, the networks have different subnet mask , its enough to avoid the overlapping
If you say so Sir Andres_P.
If you say so Sir Andres_P.
Agreed - has to be C as VNet1 and VNet2 overlap with both the address space and subnets. See here: https://www.microsoftpressstore.com/articles/article.aspx?p=2873369 "The address space is the most critical configuration for a VNet in Azure. This is the IP range for the entire network that will be divided into subnets. The address space can almost be any IP range that you wish (public or private). You can add multiple address spaces to a VNet. To ensure this VNet can be connected to other networks, the address space should never overlap with any other networks in your environment. If a VNet has an address space that overlaps with another Azure VNet or on-premises network, the networks cannot be connected, as the routing of traffic will not work properly."
Correct, chances are they change the table during the exam. different IPs. good catch
Agree with ExamPrep. https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-manage-peering#create-a-peering Virtual network: Select the virtual network you want to peer with. You can select a virtual network created through either Azure deployment model. If you want to select a virtual network in a different region, you must select a virtual network in a supported region. You must have read access to the virtual network for it to be visible in the list. If a virtual network is listed, but grayed out, it may be because the address space for the virtual network overlaps with the address space for this virtual network. If virtual network address spaces overlap, they cannot be peered. If you checked the Resource ID checkbox, this setting isn't available. In the question, VNet1 address space (10.11.0.0 - 10.11.255.255) and VNet2 address space (10.11.0.0 - 10.11.127.255) are overlapping with each other. So we can't setup peering between these 2 networks. So, the answer is C. VNet3 and VNet4 only.
the correct answer is C - only vnet3 and vnet4. I was quite certain about it as the Addresses are overlapping but i checked on multiple sites and everywhere the answer was all the three vnets so i tried it myself to just clear it. i Could not do the peering so for sure the answer is vnet3 and vnet 4 only. Cheers.
It cannot connect to vnet2! Region has nothing to do but the IPs are overlapping so in the portal u wont even see vnet2 while creating ur vnet peering.
it has to be C.
i did practically. vnet3 an vnet4 is correct. vnet1 and vnet2 are overlaping
https://www.examtopics.com/exams/microsoft/az-102/view/10/ - Correct ans C @ExamTopic : please update in Az-103 document in also .
Answer: C Just tested. You can't peer Vnets if their address space overlaps.
Came in exam 07/29/2020.
IPs table were exactly like this in the question
what was the answer? C? because of the overlap?
what was the answer? C? because of the overlap?
The correct answer is C. Please, modify it asap.
C. VNet3 and VNet4 only
they are located at differeent region is it possible to peering for all zones
you can use global peering so the answer should be Vnet 2, Vnet3 and Vnet4
The given answer is correct, you can peer all other Vnet to Vnet1, peering has nothign to do with region/physicall location.
peering is nothing to do with location but what about overlapping?? it must be VNet 3 and VNet4 only, so answer is C
In the given configuration the answer is C, but no way these will be the exact IPs in the test they will most likely not have overlapping address spaces on the test thus the answer would be D
In the given configuration the answer is C, but no way these will be the exact IPs in the test they will most likely not have overlapping address spaces on the test thus the answer would be D
Correct answer is C. Because Vnet1 address space overlap with Vnet2.
tested it is not working with Vnet2 so Vnet3 and Vnet4 is the correct answer
Answer: C https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq#:~:text=overlapping%20address%20ranges%3F-,No.,overlap%20to%20enable%20VNet%20Peering. Can I peer two VNets with matching or overlapping address ranges? No. Address spaces must not overlap to enable VNet Peering.
Answer to the question is C. You can't create VNET peering to virtual networks in the same region. However, VNET3 and VNET4 belong to different regions which makes it ideal to connect.
I created vnet with exact same config and when tried to peer vnet1 and vnet2 then i could see azure says it cannot be peered . Hence answer is C
First thoughts D because global peering Then i read https://azure.microsoft.com/en-gb/updates/global-vnet-peering-general-availability/ North Europe not available to peer across regions Now think C
Not sure about North Europe but I think it also available [https://azure.microsoft.com/en-us/updates/general-availability-global-vnet-peering/] says "Global VNet Peering is now generally available in all Azure public regions, excluding the China, Germany, and Azure Government regions."
That was a message from 30th of March 2018, in the same message there is a link to an actual overview, there it says, as of 30th of april 2018 peering is in all regions: Global VNet Peering is now generally available in all Azure public regions, excluding the China, Germany, and Azure Government regions.
It would be vnet3 and vnet4.....since vnet2 is overlapping address space..
its a trick question. if you look at the subnetting. B will go into A. thus the answer is C. VNet3 and VNet4 only.
C should be correct, check this out https://github.com/Azure/acs-engine/issues/3139
The answer is C. Please modify it.
C is right answer.
Answer C is correct as VNet1 and VNet2 have overlapping IP's
C. VNET2-VNET4
Agree with appcloudAdmin. https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq#:~:text=overlapping%20address%20ranges%3F-,No.,overlap%20to%20enable%20VNet%20Peering Answer should be C.
Answer: C. VNet3 and VNet4 only
tested this- only Vnet3 and vnet4. interestingly it allows you to create the vnet2 with subnet with a warning.
we are able to peer using global peering?
The given answer (D) is correct. The VNet1 and VNet2 have overlap. but there is no overlap between VNet2, VNet3, and VNet4 so they can peer with each other. The only limitation is with VNet1 and VNet2, These 2 cannot peer with each other or peer with any other VNET that is already peered with ano of them. e.g. if VNet 3 is peered with VNet2, VNent3 cannot peer with VNet1 due to overlapping rule.
The question was: "To which virtual networks can you establish a peering connection from VNet1?" In light of this, I believe it's C..
the anwer is correct they ask you for vnet1. you do 1 to 1 conecction vnet1 to vnet2 , vnt1 to vnet3, vnet1 to vnet4 .