Skip to main content
Answer confirmed
Question

You have an Azure virtual machine named Server1 that runs a network management application. Server1 has the following network configurations:

  • Network interface: Nic1
  • IP address: 10.1.1.1/24
  • Connected to: Vnet1/Subnet1

You need to connect Server1 to an additional subnet named Vnet1/Subnet2.
What should you do?

Proposed answer
  • A. Modify the IP configurations of Nic1.
  • B. Add an IP configuration to Nic1.
  • C. Add a network interface to Server1.
  • D. Create a private endpoint on Subnet2.
Suggested answer
  • C. Add a network interface to Server1.
Correct answer

The suggested answer is correct

C. Add a network interface to Server1.

All IP configurations on a single NIC must be associated to the same subnet. If multiple IPs on different subnets are desired, multiple NICs on a VM can be used. To learn more about multiple NICs on a VM in Azure, see Create VM with Multiple NICs.

Reference

Comments

 

Ksk08

2 weeks, 5 days ago 

Answer is C

upvoted 1 times 

Ksk08

3 weeks, 6 days ago 

I would say B How to Connect Server1 to Another Subnet What You Need to Do: Add an IP Configuration to Nic1. Why This Works: Single Network Interface (NIC): Server1 has one NIC (Nic1). You can add more settings (IP configurations) to this NIC. Multiple Subnets: By adding an IP configuration, you can give Nic1 an IP address from the new subnet (Subnet2). This lets Server1 talk to devices in that subnet. Easier Management: It’s simpler to manage one NIC with multiple IPs than to create a whole new NIC. Why Not Add a New NIC? Adding a new NIC means you have to stop the VM, create the new NIC, and connect it. That’s more work and not necessary when you can just add an IP to the existing NIC.

upvoted 1 times 

004b54b

2 months, 3 weeks ago 

Selected Answer: C

New NIC, because as highlighted by mohamed1999, adding a secondary IP configuration to the existing NIC won't be possible: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal

Note All IP configurations on a single NIC must be associated to the **same subnet**. If multiple IPs on different subnets are desired, multiple NICs on a VM can be used. To learn more about multiple NICs on a VM in Azure, see Create VM with Multiple NICs.

upvoted 2 times 

sardonique

3 months, 1 week ago 

correct, this one is a no brainer

upvoted 1 times 

SIAMIANJI

6 months, 2 weeks ago 

Selected Answer: C

You need a new NIC.

upvoted 2 times 

dfguss

6 months, 3 weeks ago 

Add a secondary IP configuration to the existing network interface (Nic1). This is the simplest and most efficient way to achieve connectivity in basic scenarios.

upvoted 1 times 

004b54b

2 months, 3 weeks ago 

As highlighted by mohamed1999, adding a secondary IP configuration to the existing NIC won't be possible: https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal Note All IP configurations on a single NIC must be associated to the **same subnet**. If multiple IPs on different subnets are desired, multiple NICs on a VM can be used. To learn more about multiple NICs on a VM in Azure, see Create VM with Multiple NICs.

upvoted 2 times 

mohamed1999

6 months ago 

This will give you a second IP in the same subnet. This will not help you.

upvoted 2 times 

MichalGr

7 months ago 

I would say B.

upvoted 1 times 

syu31svc

1 year, 8 months ago 

Selected Answer: C

A network interface (NIC) is the interconnection between a virtual machine and a virtual network. A virtual machine must have at least one NIC. A virtual machine can have more than one NIC, depending on the size of the VM you create. To learn about the number of NICs each virtual machine size supports, see VM sizes. You can create a VM with multiple NICs, and add or remove NICs through the lifecycle of a VM. Multiple NICs allow a VM to connect to different subnets. C for correct

upvoted 3 times 

MasterMani

2 years, 1 month ago 

Selected Answer: C

Correct Answer:C https://learn.microsoft.com/en-us/azure/virtual-network/network-overview

upvoted 4 times 

edykss

2 years, 2 months ago 

Answer is correct

upvoted 3 times