You have a System Center Operations Manager 2007 environment. You need to list all the processes that are running on one of the Microsoft SQL Server computers. The collection should occur only when the SQL Server state changes to unhealthy. You need to collect theinformation even if there is no administrator present. What should you do?

A.
Run the List Processes task.

B.
Run a PowerShell script that will return all processes.

C.
Create a diagnostic task for the affected SQL Server monitor. Use the tasklist.exe command and the default options.

D.
Create a rule by using the Timed Commands template. Specify the tasklist.exe command, and use the default options.

Explanation:
C: CORRECT
Tasks
As with views, there are tasks that are available when Operations Manager is installed, tasks that are imported along with management packs, and tasks that you can create on your own. Since there are so many tasks available from the default and imported management packs, you should verify whether a task that can perform the action you need already exists. Of course, there are those tasks that are part of sealed management packs that you do not have access to outside of the management pack. If this is the case, you may very well have to duplicate the functionality of the task.
Tasks come in two flavors: command-line tasks and scripts. Command-line tasks allow you to create a single command that is run on either the management server or the agent. Scripts can be written and then targeted to the management server or agent in order to run on them. With either of these approaches, the operator can select a system to target, and then run the task manually from the Operations Console. These manually run tasks enable the operators to run diagnostic tasks to help determine what is wrong, or run recovery tasks to help solve the problem causing the alert.