Exam AZ-300 topic 1 question 7 discussion

I thin VM2 cannot ping VM3, because they didn't establish bi-direction connection

Ans: Y,N,N . source: https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq ----- If your peering connection is in an Initiated state, this means you have created only one link. A bidirectional link must be created in order to establish a successful connection. For example, to peer VNet A to VNet B, a link must be created from VNetA to VNetB and from VNetB to VNetA. Creating both links will change the state to Connected.

Answer is Y,N,N

The answer is Yes, No, No. ICMP need peering both directions to work. The peering status shows disconnected when only one direction is peered. I had it peered bidirectionally, and testing ping both ways and it worked. Then in removed one peer direction and this caused the ping test to fail. For a yes, yes, no answer, VNET3 > VNET2 would also have to be peered, which is missing from the list.

Correct answer is Yes, No, No as only VM1 and VM3 have bi-directional peering

Answer should be Yes, no, no.

the correct answer is: Yes, No, No

YES, NO , NO

YNN If your peering connection is in an Initiated state, this means you have created only one link. A bidirectional link must be created in order to establish a successful connection. For example, to peer VNet A to VNet B, a link must be created from VNetA to VNetB and from VNetB to VNetA. Creating both links will change the state to Connected. https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq

When peering two virtual networks created through Resource Manager, a peering must be configured for each virtual network in the peering. You see one of the following types for peering status: Initiated: When you create the peering to the second virtual network from the first virtual network, the peering status is Initiated. Connected: When you create the peering from the second virtual network to the first virtual network, its peering status is Connected. If you view the peering status for the first virtual network, you see its status changed from Initiated to Connected. The peering is not successfully established until the peering status for both virtual network peerings is Connected. --> https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-manage-peering It needs to be configured both ways for the peering to become Connected. Y N N

Same question I found in Udemy, the answer is Y, N, N

Guys you can easily setup this in the lab and then you will see the answer is definitely Y N N. For ping to work correctly you need bidirectional connection, it won't work in uni direction since it requires a response from other side. If the question was asking ssh then it would be Y Y N.

Yes,No,No

Answer is YES, NO , NO

It is: Yes No No Even in the link they have provided it says that peering must be on both sides. I've also logged into Azure Portal and message I got when I tried peering is "For peering to work, a peering link must be created from vnet1 to remote virtual network as well as from remote virtual network to vnet1."

VM1 -> VM3 = Yes; peering in both VMs enabled VM2 -> VM3 = No; because VM3 can't reply back to VM2 VM2 -> VM1 = No; No peering between 1&2

I totally agree that answer is YYN . 1. Peered VNET are now bidirectional at the time of creation ( if you choose to do so) so in this case its clear that all the peered network will be able to communicate. There is no mention for Classic mode. Its Yes | Yes | NO I m writing this comment i m running the practical lab,