nerdexam
Cisco

352-001 · Question #63

In which two ways is IPv4 and IPv6 traffic handled in a network design that uses QoS deployment options? (Choose two.)

The correct answer is A. IPv6 and IPv4 traffic is treated in the same way by using a single QoS policy that classifies and D. IPv6 traffic is treated differently than IPv4 by using two different QoS policies. In QoS design, IPv4 and IPv6 traffic can be handled either under a unified single policy or under separate per-protocol policies, depending on whether differentiated treatment is required.

Design Considerations

Question

In which two ways is IPv4 and IPv6 traffic handled in a network design that uses QoS deployment options? (Choose two.)

Options

  • AIPv6 and IPv4 traffic is treated in the same way by using a single QoS policy that classifies and
  • BIPv6 traffic is treated differently than IPv4 by using the flow-label field, which is built into the IPv6
  • CIPv6 traffic does not require QoS because it uses to the flow-label field, which classifies and matches
  • DIPv6 traffic is treated differently than IPv4 by using two different QoS policies.
  • EIPv6 traffic is treated differently than IPv4 because it uses only the DSCP value and not the IP precedence.

How the community answered

(21 responses)
  • A
    71% (15)
  • B
    19% (4)
  • C
    5% (1)
  • E
    5% (1)

Why each option

In QoS design, IPv4 and IPv6 traffic can be handled either under a unified single policy or under separate per-protocol policies, depending on whether differentiated treatment is required.

AIPv6 and IPv4 traffic is treated in the same way by using a single QoS policy that classifies andCorrect

A single MQC (Modular QoS CLI) policy can classify and match both IPv4 and IPv6 traffic using common fields such as DSCP, allowing identical treatment without maintaining duplicate policy configurations.

BIPv6 traffic is treated differently than IPv4 by using the flow-label field, which is built into the IPv6

While IPv6 includes a 20-bit flow-label field, it is not reliably used to differentiate QoS treatment in Cisco IOS QoS policy frameworks; DSCP remains the standard classification mechanism for both IPv4 and IPv6.

CIPv6 traffic does not require QoS because it uses to the flow-label field, which classifies and matches

The IPv6 flow-label field does not automatically classify or match traffic for QoS purposes and does not eliminate the need for explicit QoS policy configuration; QoS is still required for IPv6 networks.

DIPv6 traffic is treated differently than IPv4 by using two different QoS policies.Correct

When different treatment is needed for IPv4 and IPv6, two separate QoS policies can be applied - one matching IPv4 traffic and another matching IPv6 traffic - giving the designer full independent control over each protocol's classification and queuing behavior.

EIPv6 traffic is treated differently than IPv4 because it uses only the DSCP value and not the IP precedence.

IPv6 uses a Traffic Class field that supports DSCP markings in the same way IPv4 does, and Cisco IOS QoS can match IP precedence values from the Traffic Class field; it is not restricted to only DSCP.

Concept tested: IPv4 and IPv6 unified vs. separate QoS policy design

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

#IPv6 QoS#QoS policy#DSCP#flow label

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 352-001 Practice