Which two of the following statements about CBWFQ are correct? (Choose two.)
A.
The CBWFQ scheduler provides a guaranteed amount of minimum bandwidth to each class.
B.
CBWFQ services each class queue using a strict priority scheduler.
C.
The class-default queue only supports WFQ.
D.
Each CBWFQ traffic class is policed using a congestion aware policer.
E.
Inside a class queue, processing is always FIFO, except for the class-default queue.
Explanation:
A protocol-dependent switching process handles traffic arriving at a router interface. The switching process includes delivery of traffic to an outgoing interface buffer. First-in, first-out (FIFO) queuing is the classic algorithm for packet transmission. With FIFO, transmission occurs in the same order as messages are received. Until recently, FIFO queuing was the default for all router interfaces. If users require traffic to be reordered, the department or company must establish a queuing policy other than FIFO queuing.
Cisco IOS software offers three alternative queuing options: Weighted fair queuing (WFQ) prioritizes interactive traffic over file transfers in order to ensure satisfactory response time for common user applications. Class-based weighted fair queuing (CBWFQ) in IOS 12.2 prioritizes traffic based on user-defined classes. Low latency queuing (LLQ) (IOS 12.2) brings strict priority queueing to Class-Based Weighted Fair Queuing (CBWFQ).
Class-based weighted fair queuing (CBWFQ) extends the standard WFQ functionality to provide support for user-defined traffic classes. By using CBWFQ, network managers can define traffic classes based on several match criteria, including protocols, access control lists (ACLs), and input interfaces. A FIFO queue is reserved for each class, and traffic belonging to a class is directed to the queue for that class. More than one IP flow, or "conversation", can belong to a class. Once a class has been defined according to its match criteria, the characteristics can be assigned to the class. To characterize a class, assign the bandwidth and maximum packet limit. The bandwidth assigned to a class is the guaranteed bandwidth given to the class during congestion. CBWFQ assigns a weight to each configured class instead of each flow. This weight is proportional to the bandwidth configured for each class. Weight is equal to the interface bandwidth divided by the class bandwidth. Therefore, a class with a higher bandwidth value will have a lower weight.
By default, the total amount of bandwidth allocated for all classes must not exceed 75 percent of the available bandwidth on the interface. The other 25 percent is used for control and routing traffic.
The queue limit must also be specified for the class. The specification is the maximum number of packets allowed to accumulate in the queue for the class. Packets belonging to a class are subject to the bandwidth and queue limits that are configured for the class.