Your network contains an Active Directory domain named contoso.com. The domain contains two member
servers named Server1 and Server2. All servers run Windows Server 2012 R2.
Server1 and Server2 have the Hyper-V server role installed. The servers are configured as shown in the
following table.
You add a third server named Server3 to the network. Server3 has Intel processors.
You need to move VM3 and VM6 to Server3. The solution must minimize downtime on the virtual machines.Which method should you use to move each virtual machine?
To answer, select the appropriate method for each virtual machine in the answer area.
Hot Area:
Answer: 
Explanation:
VM3: export/import is the only option due to different processor manufacturers VM6: Live migration can be
used as both have Intel CPU’s
Live Storage Migration requires same processor manufacturers Live migration requires same same processor
manufacturers
Quick migration has downtime
http://technet.microsoft.com/en-us/library/dd446679(v=ws.10).aspx
http://technet.microsoft.com/en-us/library/hh831656.aspx
http://technet.microsoft.com/en-us/library/jj628158.aspx
According to the live migration requirements, they are all met to allow a live migration from server 2 to server 3. There would have to be some configuration to allow it to migrate, but it can migrate.
Based on the question “the solution must minimize downtime on the virtual machines.” I would also say live migration for both as there is no down time and for VM3 just need to enable cpu compatibility.
You cannot use any form of migration from one server to another server if they have different processor manufacturers. The only solution for VM3 is export and import. The compatibility setting will still need to be enabled to do the export and import.
This is similar to VMware’s EVC: you can perform the migration but keeping in mind that your hyervisor server has the same manufacturer and similar processor family.
There is no way to move a VM from a AMD host to an Intel host.
This is regarding CPU micro code virtualization. When you run a VM on a AMD CPU, the microcode is different from Intel Microcode, so if you could live migrate the VM, it could cause a BSOD.
my 2ct.:
1. the 3rd link is inappropriate because the article is about SCVMM, wich is not stated to be implemented
2. the 1st liked article is also inappropriate because it’s about 2008R2 describing failover clusterin necessary for live migration, but in 2012(R2) the feature was updated and is capable of getting the job done. You just have to enable it:
https://msdn.microsoft.com/en-us/library/jj134199(v=ws.11).aspx#BKMK_Step2
https://technet.microsoft.com/en-us/library/dn859550(v=ws.11).aspx
Live migration Requirements – NOT THE RIGHT ANSWER
Common requirements for any form of live migration:
Two (or more) servers running Hyper-V that:
Support hardware virtualization.
Use processors from the same manufacturer. For example, all AMD or all Intel.
Belong to either the same Active Directory domain, or to domains that trust each other.
Virtual machines must be configured to use virtual hard disks or virtual Fibre Channel disks (no physical disks). For more information on virtual Fibre Channel, see Virtual Fibre Channel.
Use of an isolated network, physically or through another networking technology such as VLANs, is recommended for live migration network traffic.
Requirements for live migration in a cluster:
Windows Failover Clustering is enabled and configured.
Cluster Shared Volume (CSV) storage in the cluster is enabled.
Live Migration and Quick Migration require that the Hyper-V servers already be setup in a cluster.
If there is no cluster configured, the VM can still be Moved using Hyper-V Manager, however this would require a storage migration along with a virtual machine move. If a shared storage pool between the servers is being used for the VM drive storage, the Virtual Machine itself would need to be moved to a new location on the 2nd server (it can not be the same path as the original vm if it is stored on shared storage).
I’m going to assume that the Hyper-V servers are clustered, in which case the selected answers are correct.
Answer is what is shown for the question.
Microsoft refers to the Move operation on a running VM in a non clustered setup as a Live Migration (even though it is a move operation from Hyper-V Manager).
As such Live Migration would be a valid answer for the servers with the same CPUs.
https://technet.microsoft.com/en-us/library/jj134199(v=ws.11).aspx