----
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 need to ensure that your backup will continue if any invalid checksum is encountered.
Which backup option should you use?

• A. STANDBY
• B. DBO_ONLY
• C. FULL
• D. RESTART
• E. Differential
• F. CONTINUE_AFTER_ERROR
• G. SKIP
• H. CHECKSUM
• I. COPY_ONLY
• J. SIMPLE
• K. NORECOVERY
• L. Transaction log
• M. BULK_LOGGED
• N. NO_CHECKSUM

You are developing a SQL Server Integration Services (SSIS) package to implement an incremental data load strategy. The package reads data from a source system that uses the SQL Server change data capture (CDC) feature.
You have added a CDC Source component to the data flow to read changed data from the source system.
You need to add a data flow transformation to redirect rows for separate processing of insert, update, and delete operations.
Which data flow transformation should you use?

• A. Merge Join
• B. DQS Cleansing
• C. Pivot
• D. CDC Splitter

You develop a SQL Server Integration Services (SSIS) package that imports Windows Azure SQL Database data into a data warehouse every night.
The Windows Azure SQL Database data contains many misspellings and variations of abbreviations. To import the data, a developer used the Fuzzy Lookup transformation to choose the closest-matching string from a reference table of allowed values. The number of rows in the reference table is very large.
If no acceptable match is found, the Fuzzy Lookup transformation passes a null value. The current setting for the Fuzzy Lookup similarity threshold is 0.50.
Many values are incorrectly matched.
You need to ensure that more accurate matches are made by the Fuzzy Lookup transformation without degrading performance.
What should you do?

• A. Decrease the maximum number of matches per lookup.
• B. Change the Exhaustive property to True.
• C. Change the similarity threshold to 0.55.
• D. Change the similarity threshold to 0.40.

You are developing a SQL Server Integration Services (SSIS) project with multiple packages to copy data to a Windows Azure SQL Database database.
An automated process must validate all related Environment references, parameter data types, package references, and referenced assemblies. The automated process must run on a regular schedule.
You need to establish the automated validation process by using the least amount of administrative effort.
What should you do?

• A. Store the System::ExecutionInstanceGUID variable in the custom log table.
• B. Create a SQL Server Agent job to execute the SSISDB.catalog.validate_package stored procedure.
• C. View the All Messages subsection of the All Executions report for the package.
• D. Enable the SSIS log provider for SQL Server for OnTaskFailed in the package control flow.
• E. Deploy the .ispac file by using the Integration Services Deployment Wizard.
• F. Use an event handler for OnError for each data flow task.
• G. Create a table to store error information. Create an error output on each data flow destination that writes OnError event text to the table.
• H. Store the System::ServerExecutionID variable in the custom log table.
• I. Enable the SSIS log provider for SQL Server for OnError in the package control flow.
• J. Use an event handler for OnTaskFailed for the package.
• K. Deploy the project by using dtutil.exe with the /COPY SQL option.
• L. Store the System::SourceID variable in the custom log table.
• M. Use an event handler for OnError for the package.
• N. Create a SQL Server Agent job to execute the SSISDB.catalog.create_execution and SSISDB.catalog.*tart_execution stored procedures.
• O. View the job history for the SQL Server Agent job.
• P. Create a SQL Server Agent job to execute the SSISDB.catalog.validate_project stored procedure.
• Q. Deploy the project by using dtutil.exe with the /COPY DTS option.
• R. Create a table to store error information. Create an error output on each data flow destination that writes OnTaskFailed event text to the table.