A company plans to upgrade a SharePoint 2010 farm to SharePoint Server 2013. The site collection
administrators will upgrade the SharePoint sites. The SharePoint 2013 environment contains a web application
dedicated to the upgrade process.
You need to migrate SharePoint 2010 content to the SharePoint 2013 environment. Before completing the
upgrade process, you must ensure that all required customizations have been deployed.
Which three actions should you perform in sequence? (To answer, move the appropriate actions from the list of
actions to the answer area and arrange them in the correct order.)
Select and Place:
Answer: 
Explanation:
Box 1: In the SharePoint 2013 farm, restore the SharePoint Server 2010 databases.
Box 2: Run the Mount-SpContentDatabase Windows PowerShell cmdlet.
Box 3: Run the Test-SPContentDatabase Windows PowerShell cmdlet.
Note:
* You must use the Mount-SPContentDatabase cmdlet to attach a content database to a web application.
* (incorrect) Using the SharePoint Central Administration pages to attach a content database is not supported
for upgrading.
* This is the fourth phase in the process to upgrade SharePoint 2010 Products data and sites to SharePoint
2013. The process includes the following phases that must be completed in order:
1.Create the SharePoint 2013 farm for a database attach upgrade 2.Copy databases to the new farm for
upgrade to SharePoint 2013 3.Upgrade service applications to SharePoint 2013
4.Upgrade content databases to SharePoint 2013 (this phase)
5.Upgrade site collections to SharePoint 2013
* Test-SPContentDatabase
Tests a content database.
Use the Test-SPContentDatabase cmdlet to test a content database against a Web application to verify all
customizations referenced within the content database are also installed in the web application.
This cmdlet can be issued against a content database currently attached to the farm, or a content database that
is not connected to the farm. It can be used to test content databases from SharePoint 2010 Products and from
SharePoint Products and Technologies.
* (incorrect) There is no method Move-SPWebApplication
Upgrade content databases to SharePoint 2013
————————————————————————————————————————————
Rosa (7.05.2015): Shouldn’t it be
In SP13, restore the SP Server 2010 database
Run Test-SPContentDatabaseRun Mount-SPContentDatabase
Wayne Hendrix (19.05.2015): I agree with Rosa. You should test the waters before you mount up. And this
states that you can test first:
https://technet.microsoft.com/en-us/library/ff607941.aspx
And I believe mounting the database will cause the content to upgrade which you didn’t want to do until you
were sure all the solutions were deployed.
Alex (23.07.2015): Can we attach database in Central Administration instead of using MountSPContentDatabase?
elu (14.10.2015): Using the SharePoint Central Administration pages to attach a content database is not
supported for upgrading
J (21.10.2015): As thumbnails rule Microsoft prefer PowerShell options against user interface option if not
explicitly indicated.
for migration purpose it is expected that migration will be scripted to replicate process (test -prod)
Andre (25.02.2016): agree with Rosa, also technet says is:
https://technet.microsoft.com/en-us/library/cc263299.aspx