Note: This question is part of a series of questions that present the same scenario. Each question in the series
contains a unique solution that might meet the stated goals. Some question sets might have more than one
correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will
not appear in the review screen.
You have a server named Server1 that runs Windows Server 2016.
Server1 hosts a line-of-business application named App1. App1 has a memory leak that occasionally causes
the application to consume an excessive amount of memory.
You need to log an event in the Application event log whenever App1 consumes more than 4 GB of memory.
Solution: You create a performance counter alert data collector.Does this meet the goal?
A.
Yes
B.
No
Answer is B
Performance Counter in memory can only log
Memory: Page Faults/Sec Specifies the number of times per second that the code or
data needed for processing is not found in memory. This value should be as low as
possible, with values below 5 being acceptable. This counter includes both soft
faults (in which the required page is found elsewhere in memory) and hard faults (in
which the requested page must be accessed from a disk). Soft faults are generally not
a major problem, but hard faults can cause significant delays because disk accesses
are much slower than memory accesses. If this value is too high, you should
determine whether the system is experiencing an inordinate number of hard faults by
examining the Memory: Pages/Sec counter. If the number of hard page faults is
excessive, you should either determine what process is causing the excessive paging
or install more random access memory (RAM) in the system.
Memory: Pages/Sec Specifies the number of times per second that required
information was not in RAM and had to be accessed from disk or had to be written to
disk to make room in RAM. This value should be as low as possible, with values
from 0 to 20 being acceptable. If the value is too high, you should either determine
what process is causing the excessive paging or install more RAM in the system.
Memory: Available MBytes Specifies the amount of available physical memory in
megabytes. This value should be as high as possible and should not fall below 5
percent of the system’s total physical memory, as this might be an indication of a
memory leak. If the value is too low, consider installing additional RAM in the
system.
Memory: Committed Bytes Specifies the amount of virtual memory that has space
reserved on the disk paging files. This value should be as low as possible and should
always be less than the amount of physical RAM in the computer. If the value is too
high, this could be an indication of a memory leak or the need for additional RAM in
the system.
Memory: Pool Non-Paged Bytes Specifies the size of an area in memory used by
the operating system for objects that cannot be written to disk. This value should be a
stable number that does not grow without a corresponding growth in server activity.
If the value increases over time, this could be an indication of a memory leak.
1
14