Question 630
In a technical design review: A voice rollout must scale across hundreds of flows without reserving per-flow resources on every router. Which technical principle BEST explains the design decision?
Explanation
Correct Answer
DiffServ uses aggregated traffic classes and per-hop behaviors, which scale more naturally than per-flow RSVP-style state. The correct engineering response is: Choose a DiffServ-based class policy with consistent DSCP semantics instead of per-flow IntServ reservations. The observable check is: Voice marking persists appropriately and test congestion retains voice delay within the defined class SLA.
Incorrect Answers
DiffServ uses aggregated traffic classes and per-hop behaviors, which scale more naturally than per-flow RSVP-style state. The offered choice instead concerns a different principle: Integrated Services can request per-flow resource treatment but introduces signaling and state scalability trade-offs. Those technical conditions are not interchangeable.
DiffServ uses aggregated traffic classes and per-hop behaviors, which scale more naturally than per-flow RSVP-style state. The offered choice instead concerns a different principle: Traffic shaping buffers and schedules excess packets to smooth bursts instead of immediately discarding all excess. Those technical conditions are not interchangeable.
DiffServ uses aggregated traffic classes and per-hop behaviors, which scale more naturally than per-flow RSVP-style state. The offered choice instead concerns a different principle: PIM sparse-mode any-source multicast may use an RP to help establish shared-tree membership and source discovery. Those technical conditions are not interchangeable.