HOTSPOT -
You have peering configured as shown in the following exhibit.
Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the graphic.
NOTE: Each correct selection is worth one point.
Hot Area:
Box 1: vNET6 only -
Box 2: Modify the address space -
The virtual networks you peer must have non-overlapping IP address spaces.
References:
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-manage-peering#requirements-and-constraints
If your VNet peering connection is in a disconnected state, it means that one of the links created was deleted. In order to re-establish a peering connection, you will need to delete the link and recreate it. Ref: https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq#vnet-peering :
Agreed on your explanation, however the possible option is "Delete peering" only but not "Delete then recreate peering"
Its states 'first' so you would delete and then recreate.
You are right! Thanks for explanation
Answer 1 - vNet6 only 2 - "Delete Peering1"
i belive it will Box1 :Vnet6 only Box2:Delete peering1 as how to modify the add space without delete the peering
Box2 : Delete Peering 1 To resolve this issue, delete the peering from both virtual networks, and then re-create them. https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-troubleshoot-peering-issues
VNet6 is disconnected from the the other VNets so hosts can only communicate on VNet6 itself https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq#vnet-peering If your VNet peering connection is in a Disconnected state, it means one of the links created was deleted. In order to re-establish a peering connection, you will need to delete the link and recreate it. 2nd dropdown is delete peering1
Box2 - delete peering1
For 2nd box, "Delete peering 1 is the right option". Also mentioned here - https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-troubleshoot-peering-issues
Question is lacking details, like address space per vnet hence it's not logical to arrive at correct answer
yeah but some logic is that GW transit is enabled so no need for endpoints. Since there is not info on addresses or vNets then all that's left is to delete the peering and recreate it. Perhaps it was deleted from the other peer and just needs recreating and this is the only logical thing to do imo if we font have info on vnets/subnets
Answer is correct. Because the only option provided here is "modify the address space" which will involve delete peering, add/modify address space & create peering. So all three operations are implied to get the peering working. Just the delete operation is not useful.