What gives priority on an egress interface, for database traffic that connected on an ingress interface, without changing the CoS value?
What gives priority on an egress interface, for database traffic that connected on an ingress interface, without changing the CoS value?
To give priority on an egress interface for database traffic connected on an ingress interface without changing the CoS value, the appropriate choice would be QoS group. QoS groups are classification techniques that allow you to assign packets to a specific group, thus enabling prioritization of traffic without modifying the Class of Service value. This prioritization can be applied both on the ingress and egress interfaces, making it suitable for the requirement mentioned.
The provided answer is correct. B. Policy map In this scenario, you would use a policy map to specify the actions to be taken on the traffic, such as setting or preserving DSCP values, which can be used for prioritization in Layer 3 networks.
Given that you need a policy map to use QoS groups, and QoS groups themselves can only affect the ingress interface (whereas policy maps can be placed on the egress as well), I think B makes more sense, even if QoS groups can influence how the policy map treats the traffic. "A policy map containing the set qos-group command can only be attached as an input traffic policy. QoS group values are not usable for traffic leaving a device." https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_classn/configuration/xe-16/qos-classn-xe-16-book/qos-classn-grp-mtch-set.html
going with B
going with B
A is the Answear
A. QoS group The QoS group is a mechanism that allows you to assign a specific level of service to a particular type of traffic. It enables the network to prioritize traffic based on QoS group settings without necessarily modifying the CoS value. This helps in giving priority to specific types of traffic, such as database traffic, on the egress interface.