What are three design criteria to consider when you choose how many classes to implement in a DiffServ policy? (Choose three.)

Question

Accepted Answer

A. service provider support capabilities, which include SLA, PHB, and marking criteria Service provider SLA, PHB support, and marking criteria directly determine which classes are viable end-to-end, since DiffServ requires consistent treatment across all network domains. B. the ability to group applications and their requirements into classes Grouping applications with similar bandwidth, latency, and jitter requirements into common classes is the fundamental purpose of DiffServ class design. F. different capabilities in the network to apply PHBs and queue structures, and the ability to map Different network devices have varying PHB support and queue structures, so the number of classes must align with what can realistically be mapped and enforced throughout the entire path.

Answer

C. baseline expectations and projected growth of RSVP sessions RSVP is an IntServ signaling protocol, not a DiffServ mechanism, and its session count is irrelevant to designing the number of DiffServ classes.

Answer

D. the ability to leverage single-rate and dual-rate token bucket policers for different classes Token bucket policer types are implementation details for enforcing a class, not a criterion for deciding how many classes to create.

Answer

E. the total queue depth on the corresponding devices in the network Total queue depth is a device-level hardware parameter, not a design criterion used to determine the number of DiffServ traffic classes.

What are three design criteria to consider when you choose how many classes to implement in a DiffServ policy? (Choose three.)

Question

Options

How the community answered

Why each option

Topics

Community Discussion