Exam AZ-104 topic 4 question 5 discussion

Correct Answer: We cannot just move a virtual machine between networks. What we need to do is identify the disk used by the VM, delete the VM itself while retaining the disk, and recreate the VM in the target virtual network and then attach the original disk to it. Note: You can change the Subnet a VM is connected to after it's created, but you cannot change the VNet. Reference: https://blogs.technet.microsoft.com/canitpro/2014/06/16/step-by-step-move-a-vm-to-a-different-vnet-on-azure/ https://4sysops.com/archives/move-an-azure-vm-to-another-virtual-network-vnet/#migrate-an-azure-vm-between-vnets https://docs.microsoft.com/en-us/azure/virtual-machines/network-overview

Correct , not possible to migrate from vnet to another vnet. Must delete VM while keeping the disk. then create a new vm using the saved virtual hard disk

February 2025, Currently the movement between RG is quite simple, so to answer this question first you: "turn off the VM" Second: "detach the NIC from VNET1" and only then perform the movement between RG1 and RG2, and a third step would be to attach the NIC to VNET2. However, it is not mandatory to detach the NIC from VNET1 before moving since it could be done afterward, so currently, this question might no longer appear or might appear in a different form than described.

CORRECT

I think the correct answer should be: A. create a network interface in RG2 B. attach the new network interface to the VM C: ( not mentioned in the choices ), detach the old network interface form the VM.

Why wouldn't you just clone it from one vnet to another. You can do that now.

This question was in my exam on 31/08/2023.

Answer is still correct. See https://learn.microsoft.com/en-us/answers/questions/950529/help-with-switching-a-vm-to-another-existing-virtu?childtoview=950519#answer-950519

Is the question changed now? It says "You need to move the custom application to VNet2". While we are here discussing about moving the VM itself. Isn't there an easier method to move the app?

tested in LAB because it said -> The solution must minimize administrative effort. the Solution is: 1) "Delete VM1" 2) "Create a new Virtual Machine" it's much more work to move to the other RG, maybe upsize it, create a second nic, ...

Cleared Exam today 26 Feb, This question was there in exam.

Thank you @mlantonis for your explanations, I have passed the exam with 830,90% questions from here, I did udemy training on Microsoft learn and practice tests, and without ET would have never cleared exam in first attempt thank you all for the contribution.

Why cant you just detach the nic from vnet 1 and then attach to vnet 2?

1) "Delete VM1" 2) "Create a new Virtual Machine" One can't change the VNET from a VM. We must first delete the VM and re-create it, in the desired VNET.

Correct Answer: We cannot just move a virtual machine between networks. What we need to do is identify the disk used by the VM, delete the VM itself while retaining the disk, and recreate the VM in the target virtual network and then attach the original disk to it. Note: You can change the Subnet a VM is connected to after it's created, but you cannot change the VNet.

We cannot just move a virtual machine between networks. What we need to do is identify the disk used by the VM, delete the VM itself while retaining the disk, and recreate the VM in the target virtual network and then attach the original disk to it.

Answer is correct - Currently azure doe NOT allow for VNET migrations