Which three network management requirements are common practices in network design? (Choose three)

Question

Options

• AEnsure that all network devices have their clocks synchronized.
• BCollect SNMP poll information for future regression analysis.
• CCapture both ingress and egress flow-based packets, while avoiding duplication of flows.
• DLook at average counters instead of instantaneous counters for inconsistent and bursty KPIs, such
• EValidate data plane health, and application and services availability, with synthetic traffic.

Explanation

A, C, and E are the three correct answers.

A (Clock Synchronization) is correct because synchronized clocks via NTP are foundational to network management - without them, correlating logs across devices for troubleshooting or security analysis becomes unreliable or impossible.

C (Flow Capture Without Duplication) is correct because capturing both ingress and egress flows gives full traffic visibility, while avoiding duplication (e.g., not double-counting a flow seen on both sides of a link) keeps metrics accurate and storage efficient.

E (Synthetic Traffic Validation) is correct because proactively sending synthetic probes (e.g., IP SLA) validates that the data plane, applications, and services are actually reachable - even during periods of low or no real user traffic.

B is wrong because "regression analysis" is not a standard goal of SNMP polling. SNMP data is used for real-time monitoring, alerting, and trending - not statistical regression modeling.

D is wrong because for bursty KPIs (like queue drops or link utilization spikes), averages mask the problem. You should look at peak/maximum counters to catch bursts that averages smooth over.

Memory tip: Think ACE - Accurate time, Complete flows, Ensure reachability. If an option misrepresents how to use monitoring data (averages for bursts, SNMP for regression), it's a trap.

No community discussion yet for this question.