Exam AZ-103 All Questions

View all questions & answers for the AZ-103 exam

Exam AZ-103 topic 3 question 14 discussion

Actual exam question from Microsoft's AZ-103

Question #: 14
Topic #: 3

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have an Azure subscription that contains the resources shown in the following table.

VM1 connects to VNET1.
You need to connect VM1 to VNET2.
Solution: You create a new network interface, and then you add the network interface to VM1.
Does this meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: B 🗳️
Instead you should delete VM1. You recreate VM1, and then you add the network interface for VM1.
Note: When you create an Azure virtual machine (VM), you must create a virtual network (VNet) or use an existing VNet. You can change the subnet a VM is connected to after it's created, but you cannot change the VNet.
References:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/network-overview

by InsaneCreep at March 10, 2020, 1:58 p.m.

Comments

Submit Cancel

InsaneCreep

Highly Voted 5 years, 3 months ago

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.

upvoted 23 times

...

Shades

Highly Voted 4 years, 10 months ago

Came in exam 1st Aug 2020

upvoted 11 times

...

Gizdagyerek

Most Recent 4 years, 10 months ago

VPC peering can't be the answer because we want the VM to BE directly attached to vnet2. we gotta delete and re-create it.

upvoted 1 times

...

macco455

4 years, 12 months ago

.Vnet to Vnet(Vnet to Vnet peering should be done) Stop and deallocate the VM then delete only VM,then create the VM used by it’s old disk. Another method create a snap of the disk,them from the snap create disk then create VM from that disk. Once after attach the other disks of the old VM to the new VM.

upvoted 2 times

macco455

4 years, 12 months ago

IN which case, Answer is B. Replacing the NIC will not work to change VNETs, you need to save the disks, delete the VM, create new VM and readd the old disks.

upvoted 1 times

...

nfett

5 years ago

Can I move my services in and out of VNets? No. You cannot move services in and out of VNets. To move a resource to another VNet, you have to delete and redeploy the resource.

upvoted 1 times

...

hihedij

5 years ago

https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq#can-i-move-my-services-in-and-out-of-vnets

upvoted 1 times

...

CristianoRosa

5 years, 1 month ago

If they want to move the VM1 to VNET2 the answer would be Yes: Delete the VM1 and then recreate VM1 in VNET2 However if they want to connect VM1 to VNET2, the answer would be No: A VNET peering would be the answer.

upvoted 9 times

...

msg1021

5 years, 1 month ago

typo in description ...VNET1 and VNET2 are virtual network not VM

upvoted 5 times

...

EricTheGreat

5 years, 1 month ago

From what I have read you cannot move VMs between VNETS. You would have to delete the VM and recreate it in the new VNET or back it up and restore it to the new VNET

upvoted 1 times

...

MedRaito

5 years, 2 months ago

Even if we have the vnet in the same region as the VM, when can not change the Vnet of the VM. So the answer is correct also the note.

upvoted 1 times

...

vasanchez

5 years, 2 months ago

even if you stop your vm, if you try to create new it wont allow you to select different vNet

upvoted 1 times

...

certificatores

5 years, 2 months ago

I still think, this is yes. One virtual machine can have many network interfaces and all of them can connect to different networks. this is networking 101

upvoted 1 times

ExamPrep

5 years, 2 months ago

No - VNets cannot span regions: https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq "Can a VNet span regions? No. A VNet is limited to a single region. A virtual network does, however, span availability zones. To learn more about availability zones, see Availability zones overview. You can connect virtual networks in different regions with virtual network peering. For details, see Virtual network peering overview" The question specifically mentions changing the machine from VNET1 (West US) to VNET2 (East Asia) - this is only possible by deleting and re-creating the machine. VNet peering would be possible between VNET1 and VNET2, however, in this case you would have the VM having a NIC attached to single one of these VNETs depending on the region it was in and logically it would have access to the other - you wouldn't add both to the same VM.

upvoted 2 times

ExamPrep

5 years, 2 months ago

Just realised that doesn't answer the question about the machine itself having multiple NICs in different regions but this reinforces the point: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/multiple-nics "Virtual machines (VMs) in Azure can have multiple virtual network interface cards (NICs) attached to them. A common scenario is to have different subnets for front-end and back-end connectivity. You can associate multiple NICs on a VM to multiple subnets, but those subnets must all reside in the same virtual network (vNet)."

upvoted 6 times

FrancisFerreira

5 years, 2 months ago

This doesn't only reinforces your point. Instead, it proves it. We can't have NICs attached to different VNets in the same VM. I found that weird too, so I tried it out. Turns out you really can't!

upvoted 4 times

...

1337Troll

5 years, 2 months ago

I would setup a peering to solve this

upvoted 9 times

macco455

5 years ago

VNet peering cannot be used between VNets in different regions.

upvoted 1 times

Sir_Lit

4 years, 12 months ago

you are wrong !!! Global VNet Peering is now generally available in four additional regions: Europe West, US East 2, Asia South East, and Central US. Global VNet Peering enables resources in your virtual network to communicate across Azure regions privately through the Microsoft backbone.

upvoted 7 times

macco455

4 years, 12 months ago

Agreed. Global VNets can be created.

upvoted 2 times

...