HOTSPOT
A company has an on-premises deployment of Microsoft Exchange Server 2010 with
Service Pack 3. The company is migrating to Office 365.
During the migration, users must be able to see availability information between the onpremises deployment and Office 365.
You need to identify the appropriate mailbox migration strategy to use.
Which migration strategies are supported for this scenario? To answer, drag the appropriate
answer choices to the correct targets. Each answer choice may be used once, more than
once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Answer: 
Explanation:
Tricky, focused to much on Freee Busy. I think answer is Correct.
In Exchange 2010 and Exchange 2013, the TargetAddress property can’t be modified. This is the reason that staged Exchange migration doesn’t support migrating Exchange 2010 and Exchange 2013 mailboxes to Exchange Online.
http://technet.microsoft.com/en-us/library/jj898486(v=exchg.150).aspx
Answer correct because of the requirement of “users must be able to see availability information between the onpremises deployment and Office 365”
https://technet.microsoft.com/en-us/library/jj863291(v=exchg.150).aspx
Why IMAP is NO? It can be used for Exchange 2000 or newer!
Answer is correct for the following reasons:
Cutover Migration – No – Migration takes place over a few days and all accounts are moved to O365. The requirements indicate the need for some mailboxes to remain on-premises.
Staged Migration – No – Does not support migrating Exchange 2010/2013
Remote Move Migration – Yes
IMAP Migration – No – Only items in user’s inbox or other mail folders can be migrated.
No, No, Yes, No
I’m sorry but I’m a little confused about this question. Of course I discard IMAP migration due item type migration limitation.
For the other options, Staged migration is not allowed for Exchange 2010/2013.
https://support.office.com/en-us/article/What-you-need-to-know-about-a-staged-email-migration-to-Office-365-7e2c82be-5f3d-4e36-bc6b-e5b4d411e207
“You can’t use a staged migration to migrate Exchange 2013 or Exchange 2010 mailboxes to Office 365. Consider using a cutover migration or a hybrid email migration instead.”
A little background to help me solve mi confussion.
Availability Service resides in CAS server as it’s a web application. Cutover, Staged and Remote move migration they all made a copy of the local mailbox to the cloud.
@Justin. The request isn’t mentioning “some mailboxes must remain on-premises” for Cutover migration.
So… if migration time is not specified nor mailbox hybrid coexistence, why isn’t Cutover migration also YES knowing the client (outlook/owa) can access CAS server for availability service?
I have to agree with Fernando. Is there documentation anywhere that says during the migration (regardless if it’s over a few days or not) you can’t see availability on-premises? I tried researching this but couldn’t really find any solid information.
I agree with Fernando about staged, but i think that cant be cutover because of this
During the migration, users must be able to see availability information between the onpremises deployment and Office 365.