Overview
General Overview
ADatum Corporation has offices in Miami and Montreal.
The network contains a single Active Directory forest named adatum.com. The offices connect to each other by using a WAN link that has 5-ms latency.
A: Datum standardizes its database platform by using SQL Server
2014 Enterprise edition.
Databases
Each office contains databases named Sales, Inventory, Customers, Products, Personnel, and Dev.
Servers and databases are managed by a team of database administrators. Currently, all of the database administrators have the same level of permissions on all of the servers and all of the databases.
The Customers database contains two tables named Customers and Classifications.
The following graphic shows the relevant portions of the tables:

The following table shows the current data in the Classifications table:

The Inventory database is updated frequently.
The database is often used for reporting.
A full backup of the database currently takes three hours to complete.
Stored Procedures
A stored procedure named USP_1 generates millions of rows of data for multiple reports. USP_1 combines data from five different tables from the Sales and Customers databases in a table named Table1.
After Table1 is created, the reporting process reads data from Table1 sequentially several times. After the process is complete, Table1 is deleted.
A stored procedure named USP_2 is used to generate a product list. The product list contains the names of products grouped by category.
USP_2 takes several minutes to run due to locks on the tables the procedure accesses. The locks are caused by USP_1 and USP_3.
A stored procedure named USP_3 is used to update prices. USP_3 is composed of several UPDATE statements called in sequence from within a transaction.
Currently, if one of the UPDATE statements fails, the stored procedure fails. A stored procedure named USP_4 calls stored procedures in the Sales, Customers, and Inventory databases.
The nested stored procedures read tables from the Sales, Customers, and Inventory databases. USP_4 uses an EXECUTE AS clause.
All nested stored procedures handle errors by using structured exception handling. A stored procedure named USP_5 calls several stored procedures in the same database. Security checks are performed each time USP_5 calls a stored procedure.
You suspect that the security checks are slowing down the performance of USP_5. All stored procedures accessed by user applications call nested stored procedures.
The nested stored procedures are never called directly.
Design Requirements
Data Recovery
You must be able to recover data from the Inventory database if a storage failure occurs. You have a Recovery Time Objective (RTO) of 5 minutes.
You must be able to recover data from the Dev database if data is lost accidentally. You have a Recovery Point Objective (RPO) of one day.
Classification Changes
You plan to change the way customers are classified. The new classifications will have four levels based on the number of orders. Classifications may be removed or added in the future. Management requests that historical data be maintained for the previous classifications. Security A group of junior database administrators must be able to manage security for the Sales database. The junior database administrators will not have any other administrative rights.
A: Datum wants to track which users run each stored procedure.
Storage
ADatum has limited storage. Whenever possible, all storage space should be minimized for all databases and all backups.
Error Handling
There is currently no error handling code in any stored procedure.
You plan to log errors in called stored procedures and nested stored procedures. Nested stored procedures are never called directly.
You need to recommend a disaster recovery solution for the Dev database. What should you include in the recommendation?

• A. The full recovery model, full backups, and transaction log backups
• B. The full recovery model, full backups, and differential backups
• C. The simple recovery model and full backups
• D. The bulk-logged recovery model and full backups

You work as a Database Administrator (DBA) for a company named ABC.com.
The company uses a Microsoft SQL Server 2012 infrastructure.
You have a database named CorpDB.
A full backup of CorpDB is taken every week.
A differential backup of CorpDB is taken every night at midnight.
A transaction log backup of CorpDB is taken at 8am, 12pm, 4pm and 8pm.
You plan to deploy some changes to CorpDB at after the 4pm log backup completes.
You need to ensure that you can undo the changes quickly if the deployment fails.
During the deployment of the changes, no other changes must be made by users to the database. You need a backup and recovery strategy for deploying the changes.
Which two of the following actions would meet the backup and recovery requirements whilst ensuring the regular backup schedule is not disrupted? (Choose two.)

• A. Revert the database to the snapshot.
• B. Take a copy-only backup of the database before deploying the changes.
• C. Restore the snapshot to another server and recover the required objects from the snapshot.
• D. Take a full backup of the database before deploying the changes.
• E. Restore the database from the backup.
• F. Take a snapshot of the database before deploying the changes.

You manage a Microsoft SQL Server environment. You plan to configure Database Mail.
You need to ensure that all users can access a private Database Mail profile.
What should you do?

• A. On the tempdb database, add the DatabaseMailUserRole to userid 0.
• B. On the master database, add the DatabaseMailUserRole to the public user.
• C. On the profile, grant access to the public user.
• D. On the msdb database, add the DatabaseMailUserRole to the public user.

You deploy a database by using SQL Server 2012.
The database contains a table named Table1.
You need to recommend a solution that meets the following requirements:
* Stores the most recent data from Table1 by using the fastest storage solution possible.
* Stores the historical data from Table1 by using a slower storage solution.
What should you recommend?

• A. a database snapshot
• B. table partitioning
• C. partitioned views
• D. change data capture