Which event class should you monitor?

You are the database administrator of your company. You are creating a new trace on an instance of SQL Server 2008 named SQL1.
You want to monitor all connection events when a client requests a connection to SQL1.
You navigate to the Events Selection tab in the Trace Properties dialog box.
Which event class should you monitor?

A.
Audit Login

B.
Audit Login GDR Event

C.
Audit Login Failed

D.
ExistingConnection

Explanation:

You should monitor the Audit Login event class. SQL Server Profiler allows you to capture and save event datato a table or a file for analysis. You can create a new trace in SQL Server Profiler to capture events as they occuron an instance of SQL Server 2008. The Events Selection tab in the Trace Properties dialog box contains acomplete list of event classes and their event categories that you can configure to capture information aboutspecific events. To open the Trace Properties dialog box, you should open SQL Server Profiler, select the NewTrace
option from the File menu, and connect to an instance of SQL Server. To collect information about allconnection events when a client requests a connection to an instance of SQL Server, you should configure the Audit Login event class under the Security Audit event category. This event class allows you to capture all newconnection events since the trace was started.
You should not monitor the Audit Login GDR Event , Audit Login Failed , or ExistingConnection event classesbecause these event classes cannot be used to capture information about when a client requests a connection toan instance of SQL Server. The Audit Login GDR Event event class captures information about grant, revoke,and deny actions on Windows account login rights for the sp_grantlogin , sp_revokelogin , and sp_denylogin system stored procedures. The Audit Login Failed event class captures information about failed client loginattempts. The ExistingConnection event class captures information about properties of existing connectionswhen the trace was started.

Objective:
Optimizing SQL Server Performance

Sub-Objective:
Use Performance Studio.

References:
MSDN > MSDN Library > Servers and Enterprise Development > SQL Server > SQL Server 2008 > ProductDocumentation > SQL Server 2008 Books Online > Database Engine > Operations > Monitoring > MonitoringEvents > SQL Server Event Class Reference > Security Audit Event Category (SQL Server Profiler) > Audit LoginEvent Class MSDN > MSDN Library > Servers and Enterprise Development > SQL Server > SQL Server 2008 > ProductDocumentation > SQL Server 2008 Books Online > Database Engine > Operations > Monitoring > MonitoringEvents > SQL Server Event Class Reference