What are two reasons for instrumenting your network and network devices to collect performance data? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D.BD.
Instrumenting a network and network devices to collect performance data is important for several reasons. Below are the two reasons explained in detail:
To determine the impact of jitter and latency on application performance: Jitter is the variation in the delay of received packets, and latency is the time it takes for a packet to travel from the source to the destination. When network traffic experiences high levels of jitter and latency, it can have a significant impact on the performance of applications that depend on real-time data transfer, such as voice and video applications. By instrumenting the network and network devices to collect performance data, network administrators can monitor the levels of jitter and latency, and determine whether they are within acceptable limits. If they are not, the network administrator can take appropriate actions to optimize the network, such as adjusting QoS settings, upgrading network hardware, or optimizing network routing.
To enable capacity planning decisions: Capacity planning is the process of determining the resources required to support the future growth of a network. By instrumenting the network and network devices to collect performance data, network administrators can monitor the utilization of network resources such as bandwidth, CPU, and memory usage. This data can be used to forecast future resource requirements and identify potential bottlenecks or capacity constraints in the network. By understanding current network capacity and projected growth, network administrators can plan for future upgrades and ensure that the network can accommodate increased traffic and new applications.
Option C and D are not relevant reasons for instrumenting a network to collect performance data. Option C refers to the practice of routing traffic around constrained choke points in the network, which is a separate optimization technique that does not necessarily require performance data collection. Option D refers to the implementation of QoS, which is a technique for prioritizing network traffic and ensuring that critical applications receive the necessary resources. While performance data collection can help identify areas where QoS may be needed, it is not the primary reason for collecting performance data.