nerdexam
Cisco

300-320 · Question #294

What are the three configuration requirements for implementing Modular QoS on a router? (Choose three.)

The correct answer is B. class map D. service policy F. policy map. Cisco's Modular QoS CLI (MQC) requires three components: a class-map to classify traffic, a policy-map to define actions per class, and a service-policy to apply the policy to an interface.

Advanced WAN Services

Question

What are the three configuration requirements for implementing Modular QoS on a router? (Choose three.)

Options

  • ACoS
  • Bclass map
  • Cprecedence
  • Dservice policy
  • Epriority
  • Fpolicy map

How the community answered

(27 responses)
  • A
    4% (1)
  • B
    89% (24)
  • E
    7% (2)

Why each option

Cisco's Modular QoS CLI (MQC) requires three components: a class-map to classify traffic, a policy-map to define actions per class, and a service-policy to apply the policy to an interface.

ACoS

CoS (Class of Service) is a Layer 2 802.1p VLAN marking value used to indicate traffic priority; it is a field that can be matched in a class-map but is not itself an MQC configuration component.

Bclass mapCorrect

A class-map is required to define the traffic classification criteria, such as matching DSCP values, ACLs, or protocols, grouping packets into logical traffic classes for QoS treatment.

Cprecedence

IP Precedence is a ToS field marking used to classify traffic priority at Layer 3; it is a value that may be set or matched in MQC but is not a required structural building block of the MQC framework.

Dservice policyCorrect

A service-policy command is required to attach a named policy-map to a specific interface or sub-interface in either the inbound or outbound direction, activating the QoS policy.

Epriority

'priority' is a queuing action keyword used inside a policy-map class to configure low-latency queuing, not a standalone configuration requirement of the MQC framework.

Fpolicy mapCorrect

A policy-map is required to associate each class-map with specific QoS actions such as bandwidth allocation, queuing, policing, or shaping, defining the treatment for each traffic class.

Concept tested: Modular QoS CLI (MQC) three-component framework

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_mqc/configuration/xe-16/qos-mqc-xe-16-book/qos-mqc-oview.html

Topics

#MQC#class map#policy map#service policy

Community Discussion

No community discussion yet for this question.

Full 300-320 Practice