HOTSPOT
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.
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 processor manufacturers
Incorrect:
Quick migration has downtimeMigrating Virtual Machines and Storage Overview
http://technet.microsoft.com/en-us/library/jj628158.aspx
No mention of Shared Storage or a Cluster here so VM6 should be moved using Storage Migration (AKA “Storage Live Migration”). Live Migration only used within a Cluster or if VM is on Shared Storage.
I agree with you again! 🙂
I don’t agree with you again! 😀
I’ll go with provided answers
Agree.
Its export and import, storage migration
https://technet.microsoft.com/en-us/library/jj134199.aspx#BKMK_Step2
This article shows you how to configure and perform a live migration without using failover clustering. A live migration moves running virtual machines between servers running Hyper-V without any perceived downtime. This topic also includes instructions for configuring constrained delegation if you want to use remote management tools to perform live migrations.
Agree answer is correct in 2012R2. Other versions of OS it would be different.
Storage migration is moving VM’s to different storage on the SAME host.
This question is concerning moving to a different host. Storage migration is not applicable.
No it’s not.
Storage migrations can be performed between standalone Hyper-V hosts or CSVs in a clustered environment.
From this article: https://technet.microsoft.com/en-us/library/hh831435%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396 the type of live migration that supports migration of VM data to another host is defined as a shared nothing migration. Since that is not an option here storage migration is the correct answer for VM6.