A full backup of your database named DB1 is created automatically at midnight every day.
Differential backups of DB1 occur twice each day at 10:00 and at 16:00. A database snapshot is created every day at noon. A developer reports that he accidentally dropped the Pricelist table in DB1 at 12:30. The last update to Pricelist occurred one week ago.
You need to recover the Pricelist table. You want to achieve this goal by using the minimum amount of administrative effort. You must also minimize the amount of data that is lost. What should you do?

A.
Restore the most recent backup into a new database named DB1bak. Apply the most recent differential backup. Copy the Pricelist table from DB1bak to DB1.

B.
Delete all database snapshots except the most recent one. Restore DB1 from the most recent database snapshot.

C.
Recover DB1 from the most recent backup. Apply the most recent differential backup.

D.
Copy the Pricelist table from the most recent database snapshot into DB1.

Explanation:
SQL Server 2005 introduces the capacity for administrators to generate and use a read-only, stable view of a database. The database snapshot provides this capability without the overhead of creating a complete copy of the database or storage requirement. As the primary database diverges from the snapshot, the snapshot gets its own copy of original pages when they are modified.
The snapshot may be used to recover an accidental change to a database by simply reapplying the pages from the snapshot to the primary database. As the last snapshot was created at noon the same day that the Pricelist table was dropped and the fact that there has been no changes to the table makes it possible to just copy the table from the snapshot.