nerdexam
Cisco

350-801 · Question #398

A collaboration engineer is configuring the QoS trust boundary for Cisco UCM voice and video conferencing. Which two trust boundary configurations are valid? (choose two)

The correct answer is C. QoS trust boundaries exclude Jabber softphone running on a PC D. QoS trust boundaries can be extended to voice and video devices if the connected PCs are. The QoS trust boundary should ideally be set at the first network device that can classify and mark traffic, typically the IP Phone, and should not be extended to a PC running a softphone directly, but can include other voice/video devices if managed correctly.

Infrastructure and Quality of Service

Question

A collaboration engineer is configuring the QoS trust boundary for Cisco UCM voice and video conferencing. Which two trust boundary configurations are valid? (choose two)

Options

  • AQoS trust boundaries include all the devices directly attached to the access switch ports
  • BQoS trust boundaries can be extended to Jabber running on a PC
  • CQoS trust boundaries exclude Jabber softphone running on a PC
  • DQoS trust boundaries can be extended to voice and video devices if the connected PCs are
  • EQoS trust boundaries can be extended to voice and video devices exclusively

How the community answered

(17 responses)
  • A
    6% (1)
  • B
    6% (1)
  • C
    76% (13)
  • E
    12% (2)

Why each option

The QoS trust boundary should ideally be set at the first network device that can classify and mark traffic, typically the IP Phone, and should not be extended to a PC running a softphone directly, but can include other voice/video devices if managed correctly.

AQoS trust boundaries include all the devices directly attached to the access switch ports

Extending QoS trust boundaries to all devices directly attached to access switch ports is too broad and risky, as many end devices cannot be trusted to mark traffic correctly.

BQoS trust boundaries can be extended to Jabber running on a PC

Extending QoS trust boundaries directly to Jabber running on a PC is not recommended due to the untrusted nature of PC operating systems and their susceptibility to QoS marking manipulation.

CQoS trust boundaries exclude Jabber softphone running on a PCCorrect

A PC running Jabber softphone is generally considered an untrusted device because the PC operating system and other applications can manipulate QoS markings, potentially causing a security or policy violation, making it unsuitable for a QoS trust boundary.

DQoS trust boundaries can be extended to voice and video devices if the connected PCs areCorrect

The QoS trust boundary can be extended to dedicated voice and video devices that reliably mark traffic, especially when a PC is connected through the voice VLAN port of such a device, allowing the IP phone to apply the QoS markings before passing the traffic to the PC.

EQoS trust boundaries can be extended to voice and video devices exclusively

Stating that QoS trust boundaries can be extended to voice and video devices exclusively is not entirely accurate, as the boundary typically starts at the IP phone and the decision to extend depends on specific network design and trust models for other devices.

Concept tested: QoS trust boundary placement for collaboration endpoints

Source: https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/WAN_and_QoS/QoSDesignGuide/QoSDesignGuide.html

Topics

#QoS Trust Boundary#Cisco UCM#Endpoint QoS#Collaboration Voice/Video

Community Discussion

No community discussion yet for this question.

Full 350-801 Practice