352-001 · Question #779
Which two QoS models should be part of a network redesign to ensure that IP QoS is deployed to support data, voice and videos application? (Choose two)
The correct answer is A. Integrated Services by reserving network resources end-to-end before sending data C. Differentiated Services by categorizing application traffic into multiple classes marked directly in. The question tests knowledge of the two primary QoS architectural models: IntServ (end-to-end resource reservation) and DiffServ (traffic classification with packet markings).
Question
Which two QoS models should be part of a network redesign to ensure that IP QoS is deployed to support data, voice and videos application? (Choose two)
Options
- AIntegrated Services by reserving network resources end-to-end before sending data
- BDifferentiated Services by managing network resources to provide QoS to specific user packet
- CDifferentiated Services by categorizing application traffic into multiple classes marked directly in
- DDifferentiated Sen/ices by reserving network resources end-to-end before sending data
- EIntegrated Services by categorizing application traffic into multiple classes marked directly in the
How the community answered
(52 responses)- A87% (45)
- B8% (4)
- D2% (1)
- E4% (2)
Why each option
The question tests knowledge of the two primary QoS architectural models: IntServ (end-to-end resource reservation) and DiffServ (traffic classification with packet markings).
Integrated Services (IntServ) uses RSVP signaling to reserve bandwidth and resources along the entire end-to-end path before data transmission begins, providing guaranteed QoS for delay-sensitive traffic like voice and video.
DiffServ does not manage resources for individual user packets on a per-flow basis - it applies aggregate class-based treatment, which is a fundamental distinction from per-flow resource management.
Differentiated Services (DiffServ) classifies traffic into multiple service classes and marks packets directly in the IP header DSCP field, enabling scalable per-hop forwarding behaviors across the network without per-flow signaling.
End-to-end resource reservation before data transmission is the defining mechanism of IntServ using RSVP, not DiffServ - conflating this behavior with DiffServ misidentifies the model.
Categorizing traffic into classes using in-header markings is the defining behavior of DiffServ, not IntServ - IntServ operates via RSVP signaling and does not rely on per-class markings in the packet header.
Concept tested: IntServ vs DiffServ QoS architectural models
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_dfsrv/configuration/15-mt/qos-dfsrv-15-mt-book/qos-dfsrv-oview.html
Topics
Community Discussion
No community discussion yet for this question.