You administer a Microsoft SQL Server database named Sales. The database is 3 terabytes in size.
The Sales database is configured as shown in the following table.
You discover that all files except Sales_2.ndf are corrupt.
You need to recover the corrupted data in the minimum amount of time.
What should you do?
A.
Perform a restore from a full backup.
B.
Perform a transaction log restore.
C.
Perform a file restore.
D.
Perform a filegroup restore.
Explanation:
According to these references, this answer looks correct.
http://technet.microsoft.com/en-us/library/ms187048.aspx
http://msdn.microsoft.com/en-us/library/aa337540.aspx
Under the simple recovery model, the file must belong to a read-only filegroup.
Under the full or bulk-logged recovery model, before you can restore files, you must back up
the active transaction log (known as the tail of the log). For more information, see Back Up a
Transaction Log (SQL Server).
To restore a database that is encrypted, you must have access to the certificate or
asymmetric key that was used to encrypt the database. Without the certificate or asymmetric
key, the database cannot be restored. As a result, the certificate that is used to encrypt the
database encryption key must be retained as long as the backup is needed. For more
information, see SQL Server Certificates and Asymmetric Keys.
The correct answer is A
The best answer is C. This option will take less time than a full restore. The only issue here is that they are not telling us what recovery model is being used. For this answer I am assuming that we are using the Full recovery model.
This question is NOT about the recovery model in use. Which is more effective when about 70% of your DB files are corrupt (PRIMARY datafile inclusive)?
Full Restore or individual File Restore?!
Performing individual file restore (in real life), would be more cumbersome and time-consuming, than performing a full DB restore from a valid full backup; so, option A is the most logical answer.
I think Xactions filegroup indicates Full recovery model.
Think Microsoft….A is the right answer regardless of what You would do in your day to day work.
The key here is a 3 TB database. I guess the individual files would be about 500 GB. So a file restore is more efficient.