350-601 · Question #538
350-601 Question #538: Real Exam Question with Answer & Explanation
The correct answer is C: Create a QoS system class and specify an MTU value of 9216 bytes.. To implement a no-drop QoS class and enable jumbo frames without fragmentation on Cisco UCS, a QoS system class must be configured with no-drop settings and specify the maximum supported MTU of 9216 bytes.
Question
A QoS policy on Cisco UCS must meet these requirements: - No-drop class must be configured. - Jumbo frames must be enabled without fragmentation. Which configuration must be implemented to mast these conditions?
Options
- AConfigure slow-drain timers and specify an MTU value of 9100 bytes.
- BCreate a Flow Control Policy and specify an MTU value of 9000 bytes.
- CCreate a QoS system class and specify an MTU value of 9216 bytes.
- DConfigure Platinum system class and specify an MTU value of 9100 bytes.
Explanation
To implement a no-drop QoS class and enable jumbo frames without fragmentation on Cisco UCS, a QoS system class must be configured with no-drop settings and specify the maximum supported MTU of 9216 bytes.
Common mistakes.
- A. Slow-drain timers are a congestion management feature, not the primary mechanism for defining a 'no-drop' QoS class, and 9100 bytes is a common MTU but not the maximum supported by UCS for jumbo frames without fragmentation.
- B. Creating a Flow Control Policy manages Ethernet flow control (pause frames), but the 'no-drop' requirement is more specifically addressed by a QoS system class with PFC, and 9000 bytes is not the maximum MTU for UCS.
- D. While 'Platinum' could be a QoS class name, it does not inherently guarantee 'no-drop' without further specific configuration, and 9100 bytes is not the maximum MTU supported by UCS for jumbo frames.
Concept tested. Cisco UCS QoS System Classes and Jumbo Frame MTU
Topics
Community Discussion
No community discussion yet for this question.