DRAG DROP
You manage two solutions in separate Azure subscriptions.
You need to ensure that the two solutions can communicate on a private network.
Which three actions should you perform in sequence? To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.
Answer: 
Explanation:
Ans is correct http://msdn.microsoft.com/en-us/library/azure/dn690122.aspx
http://azure.microsoft.com/blog/2014/06/17/vnet-to-vnet-connecting-virtual-networks-in-azure-across-different-regions/
“…Connecting Two VNets in the Same Subscription
From an Azure virtual network, connecting to another virtual network is essentially the same as connecting to an on premises network via site-to-site (S2S) VPN. In this blog, we will start from scratch to create the virtual networks, the VPN gateways, and then connect them together, all within the same Azure subscription. Below lists the steps you will go through:
1.Create the virtual networks and matching local networks with cross premises connectivity
2.Create the Azure Dynamic Routing VPN gateways for the virtual networks
3.Connect the virtual networks together …”
why not the static routing gateway?
Ah! There it is:
https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-configure-vnet-to-vnet-connection/#create-the-dynamic-routing-gateways-for-each-vnet
–>VNet-to-VNet requires Azure VPN gateways with dynamic routing VPNs. Azure static routing VPN gateways are not supported.
Answer correct
Dynamic routing has to be used (traffic travels across Azure backbone – multi-hop)
What does this mean- “Add local networks to the VNets”? We either create VNets or Subnets or connect each other… not sure what ‘adding local networks to VNets’ means.
Shouldn’t we “edit the ACL on the VNet gateway to accept connections”?
In my view-
1. Create the dynamic routing gateways
2. Edit the ACLs on the gateway to accept connections
3. Connect the VPN gateways
Btw, the first link from Pras doesn’t exist anymore.
“Add local network” basically means “add the other vnet as a local network”. So in VNet1 you will add VNet2 as a local network, and then on VNet2 you will add VNet1 as a local network. It sounds confusing, and in my head it would sound better say call it a “Remote network”, but I’ve been through the process and it makes more sense when you do it. It basically means the network you want to connect to. If you have an Azure subscription then it would help if you went through the process to connect VNet-to-VNet. Just delete everything after.
Forgot to add, the answer as posted is correct:
1.Add local networks to the VNets
2.Create the dynamic routing gateways
3.Connect the VPN gateways