DRAG DROP
You administer a Microsoft SQL Server 2012 environment that contains a production SQL Server
2005 instance named SQL2005 and a development SQL Server 2012 instance named SQL2012.
The development team develops a new application that uses the SQL Server 2012 functionality. You
are planning to migrate a database from SQL2005 to SQL2012 so that the development team can
test their new application.
You need to migrate the database without affecting the production environment.
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.)
Answer: 
Explanation:
http://msdn.microsoft.com/en-us/library/ms177429.aspx
From the page mentioned at explanation:
” Note that if you restore a SQL Server 2005 or SQL Server 2008 database to SQL Server 2012, the database is automatically upgraded. “
But then there is this:
https://msdn.microsoft.com/en-us/library/bb510680(v=sql.110).aspx
“When a database is upgraded to SQL Server 2012 from any earlier version of SQL Server, the database retains its existing compatibility level if it is at least 90.”
This is odd. If you made a full backup for immediate restoration, you don’t need to restore the full backup and the transaction log backup because the latest transaction log backup would have occurred before the full backup. And yet the only restoration option is full and transaction log, thus you would have to take a full backup, then a transaction log backup after the full backup, then restore both. This is plausible. If the database is busy, take the full backup, restore it. Take a tail log backup and restore that, then increase the compatibility and cut over. If you did that, the answer provided would be wrong. The right answer would be make a full backup, make a log backup, then restore both with time in between the two restorations.
VSS can also be an attractive option. It was invented not to impact the production environment. Restoration is tricky, but then who cares, it has nothing to do with the production environment.
Four years later, it’s still debatable what the right answer is:
https://social.msdn.microsoft.com/Forums/en-US/15c345b1-45cc-4a1b-b8ec-d5fb2eb0ea99/migrating-a-database-from-sql2005-to-sql2012?forum=sqldocumentation
It’s not going to be on the test. Microsoft by now must have figured out this is a stupid question if so many people can’t answer it even open book.
http://www.aiotestking.com/microsoft/which-three-actions-should-you-perform-in-sequence-38/
http://www.aiotestking.com/microsoft/which-three-actions-should-you-perform-in-sequence-156/
I’m inclined to agree VSS is the one, after much research. The SQL writer service really gives us no excuse to consider any other solution because we’re taking a full backup right there.
https://technet.microsoft.com/en-us/library/ms175536.aspx
vss backup and restore followed by increasing to 110 seems right
1 – 5 – 7
1-5-7
Sorry God, I didn’t read carfully
Stupid question but answer seems correct
http://www.aiotestking.com/microsoft/which-three-actions-should-you-perform-in-sequence-54/
It could also be VSS backup, but better go with given answer as that seems to be the majority consensus