You create an availability group named HaContoso that has replicas named Server01/HA, Server02/HA, and Server03/HA.
Currently, Server01/HA is the primary replica.
You need to ensure that the following requirements are met:
Backup operations occur on Server02/HA.

If Server02/HA is unavailable, backup operations occur on Server03/HA.

Backup operations do not occur on Server01/HA.

How should you configure HaContoso?

• A.Set the backup preference of HaContoso to Prefer Secondary.
  Set the backup priority of Server02/HA to 20.
  Set the backup priority of Server03/HA to 10.
• B.Set the backup preference of HaContoso to Secondary only.
  Set the backup priority of Server02/HA to 20.
  Set the backup priority of Server03/HA to 10.
• C.Set the backup preference of HaContoso to Secondary only.
  Set the backup priority of Server02/HA to 10.
  Set the backup priority of Server03/HA to 20.
• D.Set the exclude replica of Server01/HA to true.
  Set the backup priority of Server02/HA to 10.
  Set the backup priority of Server03/HA to 20.

Comment: *

Name: *

Email: *

Verification: *

You administer a Microsoft SQL Server 2012 database named Contoso on a server named Server01.
You need to be notified immediately when fatal errors occur on Server01.
What should you create?

• A.a Resource Pool
• B.an Extended Event session
• C.a Database Audit Specification
• D.a Policy
• E.a SQL Profiler Trace
• F.a Server Audit Specification
• G.an Alert

Comment: *

Name: *

Email: *

Verification: *

You administer a Microsoft SQL Server 2012 instance.
After a routine shutdown, the drive that contains tempdb fails.
You need to be able to start the SQL Server. What should you do?

• A.Modify tempdb location in startup parameters.
• B.Start SQL Server in minimal configuration mode.
• C.Start SQL Server in single-user mode.
• D.Configure SQL Server to bypass Windows application logging.

Comment: *

Name: *

Email: *

Verification: *

You administer a Microsoft SQL Server database named Orders.
Users report that during peak usage periods, certain operations are taking more time than expected. Your initial analysis suggests that blocking is the cause.
You need to gather more data to be able to determine which processes are being blocked and to identify the root cause.
What should you do?

• A.Schedule a SQL Agent job to run every 60 seconds and insert the results of executing the sys.dm_os_wait_stats DMV into a table.
• B.Use System Monitor to catch the Lock Waits/sec event.
• C.Use sp_configure to set the blocked process threshold. Start a trace using SQL Server Profiler to catch the Blocked Process Report event.
• D.Start a Trace using SQL Server Profiler to catch the Lock: Deadlock event.

Comment: *

Name: *

Email: *

Verification: *

You administer a Microsoft SQL Server 2012 instance.
You need to stop a blocking process that has an SPID of 64 without stopping other processes What should you do?

• A.Execute the following Transact-SQL statement:EXECUTE sp_KillSPID 64
• B.Restart the SQL Server service.
• C.Execute the following Transact-SQL statement:KILL 64
• D.Execute the following Transact-SQL statement:ALTER SESSION KILL '64'

Comment: *

Name: *

Email: *

Verification: *