You administer a Microsoft SQL Server 2012 instance that contains a financial database hosted on a
storage area network (SAN).
The financial database has the following characteristics:
A data file of 2 terabytes is located on a dedicated LUN (drive D).
A transaction log of 10 GB is located on a dedicated LUN (drive E).
Drive D has 1 terabyte of free disk space.
Drive E has 5 GB of free disk space.
The database is continually modified by users during business hours from Monday through Friday
between 09:00 hours and 17:00 hours.
Five percent of the existing data is modified each day.
The Finance department loads large CSV files into a number of tables each business day at 11:15
hours and 15:15 hours by using the BCP or BULK INSERT commands.
Each data load adds 3 GB of data to the database.
These data load operations must occur in the minimum amount of time.
A full database backup is performed every Sunday at 10:00 hours.
Backup operations will be performed every two hours (11:00, 13:00, 15:00, and 17:00) during
business hours.
You implement log shipping of the financial database to another SQL Server 2012 instance.
You decide to failover to this secondary database.
You need to ensure that all transactions will be replicated to the secondary database.
Which backup option should you use?
A.
Differential
B.
Transaction Log
C.
FULL
D.
SIMPLE
E.
SKIP
F.
RESTART
G.
STANDBY
H.
CHECKSUM
I.
DBO_ONLY
J.
COPY_ONLY
K.
NORECOVERY
L.
NO_CHECKSUM
M.
CONTINUE_AFTER_ERROR
N.
BULK_LOGGED
Explanation:
http://technet.microsoft.com/en-us/library/ms187103.aspx
http://msdn.microsoft.com/en-us/library/ms191233.aspx
http://msdn.microsoft.com/en-us/library/ms178117.aspx
K
consensus from previous version of this dump
http://www.aiotestking.com/microsoft/which-backup-option-should-you-use-9/
0
0
K It’s norecovery because the only way to ensure no transactions are lost is to stop making transactions after the log is made. With norecovery the database is stopped and a new one can start.
0
0
If the original primary server instance is not damaged, back up the tail of the transaction log of the primary database using WITH NORECOVERY. This leaves the database in the restoring state and therefore unavailable to users. Eventually you will be able to roll this database forward by applying transaction log backups from the replacement primary database.
IN the question it says nowhere the primary is damaged so norecovery would be the way to go
0
0
K
0
0