Exam AZ-104 topic 4 question 74 discussion

A Multiple NICs allow a VM to connect to different subnets. VM must have at least one NIC. A virtual machine can have more than one NIC, depending on the size of the VM you create. Each NIC attached to a VM must exist in the same location and subscription as the VM. Each NIC must be connected to a VNet that exists in the same Azure location and subscription as the NIC. Reference: https://learn.microsoft.com/en-us/azure/virtual-network/network-overview

A virtual machine (VM) in Azure can have more than one network interface card (NIC) but it must be in the same location as the VM (WEST US). And it is fine to have resource group in difference location... it does not matter

The correct answer is option A(Yes), I will explain why option A is the correct option I got frustrated due to the lack of clear explanation, So I decided to test the scenario in my lab so I have created the resources as mentioned in the scenario Our goal is to create NIC2 in RG1 and West US right as per the documentation Each NIC attached to a VM must exist in the same location and subscription as the VM but they forget to mention about Vnet(Virtual Network) while I was creating NIC2 in RG1 I had an option select Vnet for first time I didn't select the VNET2 which is available in RG2 resource group instead I created the new Vnet for nic So I was not able to attach NIC2 on VM1 next time I noticed and create NIC2 in RG1 and select the VNET2 This time I was able to see the NIC2 on VM1 as shown in the screen shot below , Also keep this mind If you wanna attach another nic to VM you must stop the VM before you attach the new nic

A virtual machine (VM) in Azure can have more than one network interface card (NIC).

A is corerct each NIC must be in the same location and subscription as the VM.

- VM1 Location: VM1 is located in West US. - New NIC Location: The new network interface (NIC2) needs to be created for VM1. - Proposed Solution: Create NIC2 in RG1 and West US. For a network interface to be attached to a virtual machine, both the NIC and the VM must be in the same region. Since VM1 is in West US, NIC2 must also be in West US to be attached to VM1. The proposed solution suggests creating NIC2 in RG1 (which is in East US) and West US. This is contradictory because RG1 is in East US, but NIC2 needs to be in West US.

The right answer is B RGs don't matter in this case, jus the location of VM, VNET and NIC 1.1. VM1 is in westus 1.2. NIC1 is in westus conclusion: VNET2 must be in westus as well 2.1. Table states: VNET1 is in centralus conclusion 1: Any NIC and VM connecting to VNET1 must also be in centralus conclusion 2: Creating NIC2 in westus will not allow VM1 to connect to VNET1 because it's in centralus Reference: - Each NIC attached to a VM must exist in the same location and subscription as the VM. - Each NIC must be connected to a VNet that exists in the same Azure location and subscription as the NIC. Source: https://learn.microsoft.com/en-us/azure/virtual-network/network-overview#network-interfaces

Yes is right

Yes is Right

Yes, because VM and NIC should be in same region.

Although creating a resource group requires specifying a region for it to be stored in, the resources in that resource group could span multiple regions. MS site sites "Azure resource groups are specific to Azure regions. But resources in a resource group often span multiple regions."

B. No The goal is to create a new network interface named NIC2 for VM1. According to the given information, VM1 is located in West US and connects to VNET2 using NIC1. To meet the goal, NIC2 should also be created in the same region as VM1, which is West US. However, the solution states that NIC2 should be created in RG1, which is located in East US. Therefore, the solution does not meet the goal.

Answer: A The resource group the NIC is created in does not matter. What matters is the region the NIC is connected to. NIC's attached to VM's must be located in the same region as the VNET/Subnet it is connected to. The NIC must also be created in the same subscription. Multiple NICs allow a VM to connect to different subnets. VM must have at least one NIC. A virtual machine can have more than one NIC, depending on the size of the VM you create. Each NIC attached to a VM must exist in the same Region and belong to the same subscription as the VM. Each NIC must be connected to a VNet that exists in the same Azure Region and belong to the same Subscription as the NIC.

Answer: A The resource group the NIC is created in does not matter. What matters is the region the NIC is connected to. NIC's attached to VM's must be located in the same region as the VNET/Subnet it is connected to. The NIC must also be created in the same subscription. Multiple NICs allow a VM to connect to different subnets. VM must have at least one NIC. A virtual machine can have more than one NIC, depending on the size of the VM you create. Each NIC attached to a VM must exist in the same Region and belong to the same subscription as the VM. Each NIC must be connected to a VNet that exists in the same Azure Region and belong to the same Subscription as the NIC.

Why A? the question does not show the location for VNET2 is.

A is the answer. https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface?tabs=network-interface-portal#create-a-network-interface - A network interface can exist in the same, or different resource group, than the virtual machine you attach it to, or the virtual network you connect it to. - The virtual machine you add the network interface to must also exist in the same location and subscription as the network interface.

Hello guys, in this kind of questions I guess the clue is the following: VM1 connected to VNET2 with NIC1 on location West US. Then VNET2 location is West US and only the NICs on West US locations will be ok for the answers.