You are implementing network communication between two Azure Virtual Machines (VMs).
The Azure subscription resources are shown in the exhibit.
You need to ensure that vm1 can connect to vm2 using the private IP address.
What should you do?
You should create a virtual network peering between vnet1 and vnet2. You can use virtual network peering to enable connections between virtual networks in the same or different Azure regions. The traffic between Azure VMs uses the Microsoft private network only, resulting in a high-bandwidth, low-latency connection across virtual networks.
You should not add a new NIC on vm1 associated with vnet2. You can attach more network adapters on an Azure VM depending on the VM size to increase network throughput or enable connection with other virtual networks. However, all resources (the network adapter, the VM, and the virtual network) must be provisioned in the same Azure region.
You should not associate the vm2 NIC with vnet1. You can change the subnet, but not the virtual network associated with a NIC.
You should not move vm1 to resource group rg2. You can move an Azure VM to another resource group in your subscription. However, it does not affect VM connectivity or resource location. Vm1 will continue to be connected with vnet1 and in the same region (Central US).