352-001 · Question #382
What are three tools for ongoing monitoring and maintenance of a voice and video environment? (Choose three.)
The correct answer is A. active monitoring via synthetic probes to measure loss, latency, and jitter C. flow-based analysis to measure bandwidth mix of applications and their flows E. call management analysis to identify CAC failures and call quality issues. Ongoing monitoring of voice and video environments requires active synthetic probes for QoS measurement, flow-based analysis for bandwidth and application visibility, and call management tools for quality and CAC failure tracking.
Question
What are three tools for ongoing monitoring and maintenance of a voice and video environment? (Choose three.)
Options
- Aactive monitoring via synthetic probes to measure loss, latency, and jitter
- Bpassive monitoring via synthetic probes to measure loss, latency, and jitter
- Cflow-based analysis to measure bandwidth mix of applications and their flows
- Dflow-based analysis with PTP time-stamping to measure loss, latency, and jitter
- Ecall management analysis to identify CAC failures and call quality issues
How the community answered
(43 responses)- A88% (38)
- B5% (2)
- D7% (3)
Why each option
Ongoing monitoring of voice and video environments requires active synthetic probes for QoS measurement, flow-based analysis for bandwidth and application visibility, and call management tools for quality and CAC failure tracking.
Active monitoring using synthetic probes (such as Cisco IP SLA or Y.1731) generates controlled test traffic to continuously measure one-way or round-trip loss, latency, and jitter across the network path, providing real-time QoS baseline data specific to voice and video requirements.
Passive monitoring observes actual production traffic without injecting test packets; the term 'synthetic probes' is by definition an active technique, making this option a technical contradiction that describes no valid monitoring method.
Flow-based analysis (NetFlow, IPFIX, or sFlow) captures header metadata to identify the bandwidth mix of applications and individual flows, enabling administrators to verify traffic classification, detect bandwidth hogs, and perform capacity planning for voice and video.
Flow-based analysis captures sampled header metadata and does not provide the per-packet timing precision needed to accurately measure loss, latency, and jitter; those metrics require active probes or dedicated hardware timestamping tools, not flow records.
Call management analysis tools (such as Cisco CUCM CDR Analysis and Reporting or equivalent) track Call Admission Control failures, MOS scores, and per-call quality metrics, which are essential for diagnosing and resolving voice quality degradation across a large branch deployment.
Concept tested: Voice and video monitoring using active probes flow analysis call management
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipsla/configuration/xe-16/sla-xe-16-book/sla_overview.html
Topics
Community Discussion
No community discussion yet for this question.