You administer a SQL Server 2008 instance that hosts a large database. The following
backup strategy is used for the database: A full database backup is performed at 02:00 hr
every Monday. A differential backup is performed at 23:00 hr every day. A transaction

log backup is performed on an hourly basis. A power failure on Thursday causes the SQL
Server 2008 server to restart at 09:15 hr. Fifteen minutes after the server restarts, the users
report that they are unable to execute certain queries that access customer data. You
discover that the customer data is unmodified after the power failure. When you execute the
DBCC CHECKDB command on the database, you receive the following error message:
Object ID 2814307832, index ID 2, partition ID 83127819437122157, alloc unit ID
82134587923221126 (type In-row data): Page (3421:169) could not be processed. See
other errors for details. Table error: Object ID 2814307832, index ID 2, partition ID
83127819437122157, alloc unit ID 82134587923221126 (type In-row data), page
(3421:169). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 16928422 and
-8. CHECKDB found 0 allocation errors and 2 consistency errors in table ‘tbl_Customer’
(object ID 2814307832). When you execute the sp_help ‘tbl_customer’ stored procedure
you receive the following result set: index_name index_description ————-
———————————- PK clustered located on PRIMARY NCIX nonclustered located on
PRIMARY You need to ensure that the data is available as quickly as possible with minimal
effect on users. What should you do?

A.
Restore the latest full database backup. Restore the latest differential backup. Restore all
transaction log backups from the latest differential backup.

B.
Restore the latest full database backup. Restore all transaction log backups from the
latest full database backup.

C.
Drop and recreate the PK index.

D.
Drop and recreate the NCIX index.