Examkin

Question

Difficulty: MediumCreate and Configure Virtual Machines

You plan to deploy an Azure virtual machine named VM1. You configure a network interface named NIC1 for VM1 and connect it to a subnet in a virtual network named VNet1. You need to create and attach a second network interface named NIC2 to VM1. Which configuration is required for NIC2?

  1. NIC2 must be connected to VNet1.Answer
  2. B
    NIC2 must be connected to a different virtual network that is peered with VNet1.
  3. C
    NIC2 must be deployed in a different Availability Zone than VM1 to ensure network redundancy.
  4. D
    NIC2 must be associated with a Basic SKU Load Balancer if NIC1 is associated with a Standard SKU Load Balancer.

Answer

NIC2 must be connected to VNet1.
All network interfaces (NICs) attached to an Azure virtual machine must reside in the same location and subscription as the VM, and they must be connected to the same virtual network (VNet). While NIC2 can be in a different subnet than NIC1, it must be within the same virtual network (VNet1).

Step-by-Step Solution

1
Determine the network requirements for multi-NIC virtual machines in Azure.
Azure requires all network interfaces attached to a virtual machine to reside in the same virtual network.
This maintains the network boundary and routing scope for the single virtual machine instance.
2
Identify the virtual network hosting the first network interface (NIC1).
NIC1 is connected to a subnet in VNet1.
This establishes VNet1 as the virtual network boundary for VM1.
3
Apply the virtual network boundary rule to the second network interface (NIC2).
NIC2 must be connected to VNet1 (though it can be in a different subnet within VNet1).
Connecting NIC2 to any other virtual network, even a peered one, is not supported.

Key Concept

Azure Virtual Machine Multi-NIC Configuration Constraints
Rate this question

Topics

Create and Configure Virtual Machines

More questions from this topic