Incorrect: Typically, a spike is a temporary condition that might happen periodically with all counters without indicating a serious problem.

Correct: A performance spike is typically a temporary rise in activity, and it might not indicate a serious problem.

Incorrect: Not having enough virtual memory is a condition related to a specific counter and does not apply to spikes for all counters.

Incorrect: Access to the database server is a condition that would generally result in application errors and not something that would be detected through performance monitoring.

Incorrect: Performance spikes typically represent an anomaly and not a consistent trend.

Incorrect: Even though the spikes were collected for a period of a year, they were not compared against a baseline to determine if they were meaningful.

Incorrect: You do need to collect key performance counters over a period of time, but you also need to compare that data against a baseline to determine if it is meaningful.

Correct: The collection of key performance monitors that is compared against a baseline is a good method for the analysis of performance trends.

Incorrect: Manually generating an e-mail upon a logon failure is certainly not a quick and easy way of reporting failures.

Correct: You can create an alert that sends an e-mail when a certain counter threshold is exceeded or not reached.

Incorrect: Although you can set up an alert to execute an executable, it would be easier to just send an e-mail directly, using the alert.

Incorrect: You can log the failure to a database, but then another process would need to be responsible for notifying the administrator, so this would not be the quickest or easiest option.