What are two reasons for instrumenting your network and network devices to collect performance data? (Choose two.)

Question

Options

• Ato determine the impact of jitter and latency on application performance
• Bto enable capacity planning decisions
• Cto route traffic around constrained choke points in the network
• Dto determine the locations at which QoS needs to be implemented

• A
  3% (1)
• B
  94% (29)
• C
  3% (1)

Explanation

Network instrumentation means deploying monitoring tools (SNMP, NetFlow, IPSLA, etc.) to continuously collect metrics such as bandwidth utilization, latency, jitter, packet loss, and queue depths. Capacity planning (B) is a primary reason: historical and real-time performance data reveals utilization trends, identifies links approaching saturation, and informs decisions about when and where to upgrade bandwidth or add infrastructure - without this data, upgrades are guesswork. Determining QoS implementation points (D) is equally important: you cannot know which interfaces, nodes, or application flows need QoS policies until you have measured where congestion occurs, which traffic classes are impacted, and where delay-sensitive traffic competes with bulk traffic. Option A (jitter/latency impact on applications) is more of an outcome of specific active testing tools like IPSLA rather than a primary rationale for broad network instrumentation. Option C (routing traffic around choke points) describes dynamic traffic engineering, not a reason to collect performance data.

No community discussion yet for this question.