You have two subscriptions named Subscription1 and Subscription2. Each subscription is associated to a different Azure AD tenant.\nSubscription1 contains a virtual network named VNet1. VNet1 contains an Azure virtual machine named VM1 and has an IP address space of 10.0.0.0/16.\nSubscription2 contains a virtual network named VNet2. VNet2 contains an Azure virtual machine named VM2 and has an IP address space of 10.10.0.0/24.\nYou need to connect VNet1 to VNet2.\nWhat should you do first?\nA. Move VM1 to Subscription2.\nB. Modify the IP address space of VNet2.\nC. Provision virtual network gateways.\nD. Move VNet1 to Subscription2.\nCorrect Answer: C\nSection: (none)\nExplanation\nExplanation/Reference:\nExplanation:\nThe virtual networks can be in the same or different regions, and from the same or different subscriptions. When connecting VNets from different subscriptions, the\nsubscriptions do not need to be associated with the same Active Directory tenant.\nConfiguring a VNet-to-VNet connection is a good way to easily connect VNets. Connecting a virtual network to another virtual network using the VNet-to-VNet\nconnection type (VNet2VNet) is similar to creating a Site-to-Site IPsec connection to an on-premises location. Both connectivity types use a VPN gateway to\nprovide a secure tunnel using IPsec/IKE, and both function the same way when communicating.\nThe local network gateway for each VNet treats the other VNet as a local site. This lets you specify additional address space for the local network gateway in order\nto route traffic.\nReferences: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-\nportal
","frontmatter":{"date":null,"number":null,"title":"","options":null,"explanation":null,"references":null,"answer":null}},"previous":{"edges":[]},"next":{"edges":[]}},"pageContext":{"title":"60","fileAbsolutePath":"/opt/build/repo/src/data/60.md","number":null}},"staticQueryHashes":["2744294623","3649515864"]}