What should you identify?

You have a server named Server1 that runs Windows Server 2012 R2.
You discover that the performance of Server1 is poor.
The results of a performance report generated on Server1 are shown in the following table.

You need to identify the cause of the performance issue.
What should you identify?

A.
Insufficient processors

B.
Excessive paging

C.
Driver malfunction

D.
Insufficient RAM

Explanation:
Processor: %DPC Time. Much like the other values, this counter shows the amount of time
that the processor spends servicing DPC requests.
DPC requests are more often than not associated with the network interface.
Processor: % Interrupt Time. This is the percentage of time that the processor is spending
on handling Interrupts. Generally, if this value exceeds 50% of the processor time you may
have a hardware issue. Some components on the computer can force this issue and not
really be a problem. For example a programmable I/O card like an old disk controller card,
can take up to 40% of the CPU time. A NIC on a busy IIS server can likewise generate a
large percentage of processor activity.
Processor: % User Time. The value of this counter helps to determine the kind of processing
that is affecting the system. Of course the resulting value is the total amount of non-idle time
that was spent on User mode operations. This generally means application code.
Processor: %Privilege Time. This is the amount of time the processor was busy with Kernel
mode operations. If the processor is very busy and this mode is high, it is usually an
indication of some type of NT service having difficulty, although user mode programs can
make calls to the Kernel mode NT components to occasionally cause this type of
performance issue.
Memory: Pages/sec. This value is often confused with Page Faults/sec.
The Pages/sec counter is a combination of Pages Input/sec and Pages
Output/sec counters. Recall that Page Faults/sec is a combination of hard page faults and
soft page faults. This counter, however, is a general indicator of how often the system is
using the hard drive to store or retrieve memory associated data.
http://technet.microsoft.com/en-us/library/cc768048.aspx