You are the network administrator for your company. The network contains an application server running Windows Server 2003. Users report that the application server intermittently responds slowly. When the application server is responding slowly, requests that normally take 1 second to complete take more than 30 seconds to complete.
You suspect that the slow server response is because of high broadcast traffic on the network. You need to plan how to monitor the application server and to have a message generated when broadcast traffic is high. You also want to minimize the creation of false alarms when nonbroadcast traffic is high.
What should you do?
A.
Use the Alerts option in the Performance Logs and Alerts snap-in to configure an alert to trigger when the Datagrams/sec counter in the UDPv4 object is high.
B.
Use System Monitor and configure it to monitor the Datagrams/sec counter in the UDPv4 object.
C.
Use System Monitor and configure it to monitor the Segments/sec counter in the TCPv4 object.
D.
Use the Alerts option in the Performance Logs and Alerts snap-in to configure an alert to trigger when the Datagrams/sec counter in the TCPv4 object is high.
Explanation:
Performance Logs And Alerts is an MMC snap-in that uses System Monitor’s performance counters to capture information to log files over a long period of time. Although the Performance console works well when systems are actively performing poorly, when you can’t wait around, you can set up triggers using the Performance console to catch bad systems in action. UDPv4 is one of the performance objects that provide network traffic monitoring capabilities. It monitors the number of User Datagram Protocol (UDP) packets the computer transmits and receives. Service applications, such as the Domain Name System (DNS) and the Dynamic Host Configuration Protocol (DHCP), typically use UDP for clientserver communications.Reference:
Craig Zacker, MCSE Self-Paced Training Kit (Exam 70-293): Planning and Maintaining a Microsoft Windows Server 2003 Network Infrastructure, Microsoft Press, Redmond, Washington, 2004, p. 6: