Connect Azure virtual machine to additional subnet | AZ-800 Exam

C

First add another network interface to Server1, then connect it to Subnet2.

Virtual network and subnets.

A subnet is a range of IP addresses in the virtual network. You can divide a virtual network into multiple subnets for organization and security. Each NIC in a VM is connected to one subnet in one virtual network. NICs connected to subnets (same or different) within a virtual network can communicate with each other without any extra configuration.

To connect Server1 to an additional subnet named Vnet1/Subnet2, we need to ensure that the network traffic can flow between these two subnets.

Option A: Modify the IP configurations of Nic1 This option is not correct because modifying the IP configuration of Nic1 will not allow the virtual machine to be connected to an additional subnet. It only allows the virtual machine to communicate with the current subnet it is connected to.

Option B: Add an IP configuration to Nic1 This option is partially correct. We can add a secondary IP configuration to Nic1 that is associated with the Vnet1/Subnet2. This will allow the virtual machine to communicate with the resources on both subnets. However, we need to ensure that the routing is properly configured in order for traffic to flow between the subnets.

Option C: Add a network interface to Server1 This option is not necessary since we can add a secondary IP configuration to the existing network interface to achieve the same result. Adding a new network interface would also require additional configuration and may not be needed in this scenario.

Option D: Create a private endpoint on Subnet2 This option is not necessary to connect the virtual machine to an additional subnet. Private endpoints are used to enable secure access to a specific Azure service over a private IP address within a virtual network. It is not related to connecting virtual machines to subnets.

Therefore, the correct answer is option B: Add an IP configuration to Nic1.