Which characteristic of distributed class-based weighted fair queueing addresses jitter prevention?
Which characteristic of distributed class-based weighted fair queueing addresses jitter prevention?
Distributed class-based weighted fair queueing addresses jitter prevention by minimizing jitter through the implementation of a priority queue for voice traffic. This ensures that voice packets, which are sensitive to delay variations, are given preferential treatment to reduce jitter.
C. It minimizes jitter by implementing a priority queue for voice traffic.
welll B and C are the same .. so if C is correct why no B ?
B says it avoids, C says it minimizes. You can't avoid jitter, you can only minimize. B is the only one in the list that I mentally threw out all together.
B says it avoids, C says it minimizes. You can't avoid jitter, you can only minimize. B is the only one in the list that I mentally threw out all together.
C https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_conmgt/configuration/15-mt/qos-conmgt-15-mt-book/qos-conmgt-oview.html
Voting so it shows, it's C based on this information https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_conmgt/configuration/15-mt/qos-conmgt-15-mt-book/qos-conmgt-oview.html
Answer A by wording i found Class-Based Weighted Fair Queueing (CBWFQ) provides weighted fair queuing based on defined classes with no strict priority queue available for real-time traffic. CBWFQ allows <a user> (you) to define traffic classes and then assign characteristics to that class. https://www.ccexpert.us/qos-implementing/lower-priority-classes-use-cbwfq.html
answer is A https://www.cisco.com/en/US/docs/ios/12_0t/12_0t5/feature/guide/cbwfq.html#:~:text=CBWFQ%20allows%20you%20to%20specify%20the%20exact%20amount%20of%20bandwidth%20to%20be%20allocated%20for%20a%20specific%20class%20of%20traffic.%20Taking%20into%20account%20available%20bandwidth%20on%20the%20interface%2C%20you%20can%20configure%20up%20to%2064%20classes%20and%20control%20distribution%20among%20them%2C%20which%20is%20not%20the%20case%20with%20flow%2Dbased%20WFQ.
i think it's D. https://www.cisco.com/en/US/docs/ios/12_0t/12_0t5/feature/guide/cbwfq.html Feature Overview Class-based weighted fair queueing (CBWFQ) extends the standard WFQ functionality to provide support for user-defined traffic classes. For CBWFQ, you define traffic classes based on match criteria including protocols, access control lists (ACLs), and input interfaces. Packets satisfying the match criteria for a class constitute the traffic for that class. A queue is reserved for each class, and traffic belonging to a class is directed to the queue for that class.
A and D kinda say the same thing. I am going to go with D, just because it uses the word "define", which is all over Cisco documentation.
I think it is C. Because why would we allow (users) to define classes ?. QOS classes should be defined by Admins not users
Actually, I don't know I think B and C but generally B
Sorry A and C but based on Cisco DCO : Class-Based Weighted Fair Queuing (CBWFQ): Provides class bandwidth guarantee for user-defined traffic classes. It provides flow-based WFQ support for nonuserdefined traffic classes.
It could be between A and D the correct answer. B and C are incorrect, CBWFQ alonely can not offer priority queue, it must be LLQ.