350-801 · Question #10
Why would we not include an end user's PC device in a QoS trust boundary?
The correct answer is C. The end user may incorrectly tag their traffic to be prioritized over other network traffic. When it comes to QoS, it is best practice to mark packets as close to the source as possible. Most devices, such as computers and servers cannot mark their own packets and should not be trusted even if they can. Cisco phones, however, can mark their own packets and can be…
Question
Why would we not include an end user's PC device in a QoS trust boundary?
Options
- AThe end user could incorrectly tag their traffic to bypass firewalls.
- BThere is no reason not to include an end user's PC device m a QoS trust boundary
- CThe end user may incorrectly tag their traffic to be prioritized over other network traffic
- DThe end user could incorrectly tag their traffic to advertise their PC as a default gateway.
How the community answered
(47 responses)- A2% (1)
- B6% (3)
- C89% (42)
- D2% (1)
Explanation
When it comes to QoS, it is best practice to mark packets as close to the source as possible. Most devices, such as computers and servers cannot mark their own packets and should not be trusted even if they can. Cisco phones, however, can mark their own packets and can be trusted with the QoS markings they provide. Therefore, QoS trust boundaries should be set up so that the switch will trust the QoS markings phones place on their own packets
Topics
Community Discussion
No community discussion yet for this question.