You have a database that is accessed by 300 concurrent users.You need to log all of the queries that become deadlocked. The solution must meet the following requirements:
Provide a representation of the deadlock in XML format.
Minimize the impact on the server.
What should you create?

A.
A SQL Server Profiler trace

B.
A script that enables trace flags

C.
A SQL Server Agent job that retrieves information from the sys.dm_tran_active_transactions dynamic
management views

D.
A SQL Server Agent job that retrieves information from the sys.dm_tran_session_transactions dynamic
management views

Explanation:
Analyze Deadlocks with SQL Server Profiler
Use SQL Server Profiler to identify the cause of a deadlock. A deadlock occurs when there is a cyclic
dependency between two or more threads, or processes, for some set of resources within SQL Server. Using
SQL Server Profiler, you can create a trace that records, replays, and displays deadlock events for analysis.
To trace deadlock events, add the Deadlock graph event class to a trace. This event class populates the
TextData data column in the trace with XML data about the process and objects that are involved in the
deadlock. SQL Server Profiler can extract the XML document to a deadlock XML (.xdl) file which you can view
later in SQL Server Management Studio.