An administrator is looking for a data center switching solution that will greatly reduce the likelihood of dropped frames when uplink congestion is experienced.
Which AOS-CX switch queuing feature meets the administrator's needs?
An administrator is looking for a data center switching solution that will greatly reduce the likelihood of dropped frames when uplink congestion is experienced.
Which AOS-CX switch queuing feature meets the administrator's needs?
To mitigate the issue of dropped frames due to uplink congestion, the Virtual Output Queuing (VOQ) feature is the appropriate solution. VOQ helps to prevent Head-of-Line (HOL) blocking by ensuring that each egress port maintains its own queue, thereby allowing packets destined for noncongested ports to proceed without delay. This queuing method is designed to handle internal traffic efficiently and reduce the likelihood of frame drops during periods of high congestion.
As they are asking for a "feature" Shouldnt it be B? Virtual Output Queuing (VOQ) feature mitigates head-of-line (HOL) blocking
Page 43 Study Guide: The figure shows that 4 packets have arrived at some interface, sitting in a queue, waiting for service. If the ingress buffer used a single queue, Head Of Line (HOL) blocking could delay traffic. This occurs when the first packet in the queue (at the “head of the line”) is destined out a congested port, it delays all packets behind it, even though those that are destined to noncongested ports. | AOS- CX switches use an intra- switch queuing method called Virtual output Queuing ( VoQ ). VOQ prevents this problem by providing deep ingress buffers with separate queues for each egress port. [Aruba Networks]
Is it B? Because the rest of Schedule profiles while B is a queuing profile.
Is it not C? Not sure..
C and D both accomplish it, but it's the algorithm behind it. Therefore i think B is meant as a feature.
B is correct