Exam 70-740 topic 1 question 191 discussion

can you explain please why not it cant be the 2 answers export and import as its fastest way ?

Quick Migration exists in Server 2016....

I agree bcos quick migration was replaced by live migration since 2008 R2

Now if we were told that we were able to enable processor compatability with the Live Migration option for the VM1 to FC3 move from Hyper-V manager, then I think that would be a valid option. However we aren't given this level of detail or additional info in the question. All we know is that the hosts of FC1 and FC3 have differnet CPUs. If we were to attempt a Live Migration from Hyper-V manager of VM1 from a host in FC1 to a host in FC3, then it would fail because of the diferent CPUs. Unless we were able to enable processor compatability a Live Migration is not a valid option. Therefore only Export and import is left as the valid choice. The only other possability that could be, would be doing a shared nothing migration. But that gets more involved with setting up constrained delegation and haivng to move the VM to clustered storage. We are not told anything about the existance of a target clustered storage on FC3 here that would be required. https://www.itprotoday.com/server-virtualization/shared-nothing-live-migration-between-clusters

Thank you Sir, you gave the best hint. its not in the same cluster so quick will not be possible.

https://docs.microsoft.com/en-us/system-center/vmm/migrate?view=sc-vmm-2016#live-vm-migration-support-matrix Live Migration -Moves a virtual machine running as part of a failover cluster from one cluster to another.

from the microsoft website on export / import doc : https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/export-and-import-virtual-machines Import a Virtual Machine Importing a virtual machine registers the virtual machine with the Hyper-V host. You can import back into the host, or new host. If you're importing to the same host, you don't need to export the virtual machine first, because Hyper-V tries to recreate the virtual machine from available files. Importing a virtual machine registers it so it can be used on the Hyper-V host. The Import Virtual Machine wizard also helps you fix incompatibilities that can exist when moving from one host to another. This is commonly differences in physical hardware, such as memory, virtual switches, and virtual processors. so different processor should be export / import

I agree based on the article. Your answer makes the most sense.

how would he know, unless he got 100% on the exam...... he's just saying he had the question