350-401 Question #617: Real Exam Question with Answer & Explanation

Question

How must network management traffic be treated when defining QoS policies?

Options

• Aas delay-sensitive traffic in a low latency queue
• Busing minimal bandwidth guarantee
• Cusing the same marking as IP routing
• Das best effort

Explanation

QoS Treatment for Network Management Traffic

Network management traffic (SNMP, syslog, NTP, SSH management sessions, etc.) must be treated as delay-sensitive traffic placed in a low latency queue (LLQ) because timely delivery of management traffic is critical - delays in receiving alerts, polling responses, or management commands can prevent administrators from detecting and responding to network issues promptly.

Why the distractors are wrong:

• B (minimal bandwidth guarantee): Giving management traffic only minimal bandwidth risks starvation or drops during congestion, which is dangerous when you need visibility into the network most.
• C (same marking as IP routing protocols): Routing protocol traffic (CS6/CS7) has its own distinct priority class; lumping management traffic with it is incorrect and can disrupt routing adjacencies if mismanaged.
• D (best effort): Treating management traffic as best effort (DSCP 0) means it competes with all other unclassified traffic and could be dropped or severely delayed during congestion - exactly when you need it most.

Memory Tip: Think "Manage with urgency" - just as you'd want emergency access to a building during a crisis, network management traffic needs a fast lane (LLQ) during network congestion, not the general queue.

No community discussion yet for this question.