HOTSPOT -
You have an Azure subscription named Subscription1. Subscription1 contains the virtual networks in the following table:
Subscription1 contains the virtual machines in the following table:
The firewalls on all the virtual machines are configured to allow all ICMP traffic.
You add the peerings in the following table:
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:
References:
https://docs.microsoft.com/en-us/azure/virtual-network/tutorial-connect-virtual-networks-portal
I thin VM2 cannot ping VM3, because they didn't establish bi-direction connection
Must be error in question since you cannot configure unidirectional VNET peering.
Answer should be Yes, no, no. In early version of Azure, we have to create peer on each vnet. Azure improved vnet peering recently and create peering bi-direction.
You still have a choice to create unidirectional peering like in the table above. So: Yes Yes No simple table mapping
the option is called "Configure virtual network access settings". If you set "Allow virtual network access from VNET1 to VNET2" to disabled it will be unidirectional
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
the option is called "Configure virtual network access settings". If you set "Allow virtual network access from VNET1 to VNET2" to disabled it will be unidirectional
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
You still have a choice to create unidirectional peering like in the table above. So: Yes Yes No simple table mapping
the option is called "Configure virtual network access settings". If you set "Allow virtual network access from VNET1 to VNET2" to disabled it will be unidirectional
Yes, No, No
Yes, No, No
the option is called "Configure virtual network access settings". If you set "Allow virtual network access from VNET1 to VNET2" to disabled it will be unidirectional
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
Answer should be Yes, no, no. In early version of Azure, we have to create peer on each vnet. Azure improved vnet peering recently and create peering bi-direction.
You still have a choice to create unidirectional peering like in the table above. So: Yes Yes No simple table mapping
the option is called "Configure virtual network access settings". If you set "Allow virtual network access from VNET1 to VNET2" to disabled it will be unidirectional
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
the option is called "Configure virtual network access settings". If you set "Allow virtual network access from VNET1 to VNET2" to disabled it will be unidirectional
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
You still have a choice to create unidirectional peering like in the table above. So: Yes Yes No simple table mapping
the option is called "Configure virtual network access settings". If you set "Allow virtual network access from VNET1 to VNET2" to disabled it will be unidirectional
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
but not sure if ping is going to work with the unidirectional peering, have to check.
the option is called "Configure virtual network access settings". If you set "Allow virtual network access from VNET1 to VNET2" to disabled it will be unidirectional
but not sure if ping is going to work with the unidirectional peering, have to check.
but not sure if ping is going to work with the unidirectional peering, have to check.
Yes, No, No
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.
There is nothing in this question that says the connection is in an initiated state. ALso, tehre is no way to create a one way peering in the portal unless its using a classic network which there is no mention of this in the questions. SO the fact it is peered one way would make it peered the other way. SO Y,Y,N is the answer
where is downvote option...
where is downvote option...
Ans: Y, N, N 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#my-vnet-peering-connection-is-in-initiated-state-why-cant-i-connect
I think the answer is: yes-yes-no (no, because no peering vnet2 and vnet1)
You need to enable peering for both connections. Answer should be YES, NO, NO
Due to the peering's table, answer should be Y, Y, N. In fact, I don't know from when is this question, but nowadays if you create a network peering, during the creation process through the Azure Portal, when you create first way peering ask you about return way, and authomatically create both peerings.
Answer is correct, no peering between vnet2 and vnet1 so no routing, no traffic, no ping. rest of vnets are peered
The Answer is YES, YES, NO No peering between VNET1 and VNET2 Pinox1 is correct
Answer: Yes, No, No The VM2 can't connect to VM3 because the peering will be in the initiated state: Initiated state - no connection ... Only one of the pair of links has been created ... Create the 2nd link to become connected state Disconnected state - no connection ... One of the pair of links has been deleted ... Delete the link and re-create Connected state ... Running fine
YES - VNET1 to VNET3YES YES - VNET2 to VNET3 NO - no VNET2 to VNET1 You can create unidirectional connection, it will work - checked it. ping/imcp doesn't require bidirectional connection. if you have V1-V2 only, V1 will be able to pint V2 but not vise versa - tried it in lab
YES-NO-NO Just tried in a LAB. ICMP requires bi-direction connections. As soon as in a peering you set "Disabled" in Configuration\Allow virtual Network Access From Vnet3 to Vnet2 you loose ICMP.
Ummm, ICMP requires connectivity in both directions. PING is exactly that, you send a ping an wait for the reply. If you check the results of a windows ping it has packets sent and packets received. Not possible with unidirectional connection.
I hate how they word the questions. Technically VM2 can send a ping to VM3 but just not get a reply. You have to assume a successful ping / reply is what they are asking.
so true!
Configured as vnet1 <--> vnet3 vnet2 ---> vnet3 VM1 -> VM3 = Yes VM2 -> VM3 = No; because VM3 can't reply back to VM2 VM2 -> VM1 = No; No peering between 1&2 https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq#vnet-peering
Just do lab, you will know the answer is Y, N, N although newer version will create bi-direction peering for you, you can still delete one of them manually, so you can get the answer. Do the lab is easy, why don't you verify by yourself?
Yes No No
yes no no
I did the lab and tested it. YES - VM1 can ping VM3 YES - VM2 can ping VM3 But VM2 can,t ping VM1 Yes, Yes, No
well depeds. if you took this exam 5 moths ago. the answer would be Yes no no But with the recent update too Azure, the answer would be Yes yes no because azure creates the other direction of the peering now for us automatically.
i take my previous comment back. It is YYN. I am still not sure why it required #3, vnet3 to vnet1 peering but as long as u are in same subscription and have rights, you only need to peer in one direction, other direction is done for u.
Only VMs 1 and 3 have bidirectional peering, so they can ping each other. 2 and 3 cannot. 1 and 2 cannot (no peering). Answer will be: Yes, No, No. 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. 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.
This is an old question, how VNET peering works, has changed now. Given answer are correct with respect to how peering used to work before however for modern peering connections, questions is incomplete.
The answer is: Yes, No, No. Please, modify it.
I'd agree with this statement, VM2 > VM3 ping wouldn't return a successful response.
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,
Same question I found in Udemy, the answer is Y, N, N
YES, NO , NO
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.
ICMP protocol is configured only at OS level. Nothing to do with peering. Based on latest Azure setting on peering cannot be established unidirectional
Yes,Yes,No
I don't think you really do the lab.
VNET3 subnet is assigned a non-routable IP. How does this impact the peering relationships?
For peering to work, a peering link must be created from vnet2 to vnet3 as well as from vnet3 to vnet2.
if its within same subscription you dont need to, you do it at one place, which will connect both vnet. If its in different subscription, then you must do it at both side. https://docs.microsoft.com/en-us/azure/virtual-network/create-peering-different-subscriptions
I tend to go Y N N. From my understanding of PING, PING involves sending ICMP "echo request packets" to the target host and waiting for a reply. Therefore, it would seem to me that if VNet3 is not peered with VNet2, then PING (with it's echo definition) would not be successful because VNet2 would not be able to receive the packets - thus breaking the connection.
In Current version of Azure portal creates the bidirectional peering automatically. However you can disable connection from destination to source in the peering settings. Hence the question is incorrect. Earlier we had to create two peering in order to enable the bidirectional peering.
The answer should be YES, NO, NO. I tested. Not only ping doesn't work, but layer 4 also won't connect if BOTH peerings are configured. I did set up an HTTP server and I could only get it to work once I enabled both ways in the peering. Go figure.
Given answer is correct.. Y Y N note: PING involves sending ICMP
YES YES NO Now Peering single side create is OK
I dont think the question said - 1-sided peering was set ? so YYN is correct.
They all are in same subscription when you create peering from vNET1 to vNet3 it's also auto create peering from vNET3 to vNET1 that ping can work bi-directional that means VM1 can ping VM3. There peering from vNET2 to vNET3 that mean VM2 can ping VM3. As there no peering configured between vNET1 & vNET2 so ping we will no work from VM2 to VM1. I tried it in the Lab answer Y,Y,N
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."
Answer is YES, NO , NO
Yes,No,No
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
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
the correct answer is: Yes, No, No
Correct answer is Yes, No, No as only VM1 and VM3 have bi-directional peering