You are employed as a database administrator at Domain.com. The Domain.com network consists of a single Active Directory domain named Domain.com. Domain.com makes use of a SQL Server 2005 named Certkiller -DB03. You have received several complaints from users in the Sales department reporting that an order processing application stopped responding in the middle of an order transaction. The SQL Server session ID of users at Domain.com is 54. You need to determine whether session 54 is blocked by another connection.
What should you do? (Choose all that apply)

A.
You need to open the Activity Monitor in SQL Server Management Studio.
Then you can open the Locks by Process page and view the Request Mode column for session 54.

B.
You need to open the Activity Monitor in SQL Server Management Studio and open the Process Info page.
Thereafter you can view the BlockedBy column for session 54.

C.
You need to open a new query window in SQL Server Management Studio and execute the following statement: SELECT * FROM sys.dm_exec_sessionsWHERE session_id = 54. Then view the status column.

D.
You need to open a new query window in SQL Server Management Studio.
Then you can execute the following statement: SELECT * FROM sys.dm_exec_requests WHERE session_id = 54. Then view the blocking_session_id column.

Explanation:
The Process Info page shows the properties of current processes. Blocked By tells you the Process ID (SPID) of a blocking process. Blocking indicates whether this process is blocking others.
1=yes; 0=no.
The sys.dm_exec_request DMV can be used to determine whether a process is being blocked and to identify the process that is creating the blocking. If a value greater that 0 exists in the blocking_process_id column the process is being blocked by the SPID logged in the column.