Which option implements basic rate limiting per user, subnet, or interface?

Which option implements basic rate limiting per user, subnet, or interface?

• A. Simple Queue
• B. Queues
• C. Firewall
• D. Mangle

Answer: (A)

The mechanism being tested is how to apply straightforward bandwidth limits to specific targets like a user, subnet, or interface. Simple Queue is designed for exactly that: you create a queue for a target—whether a single IP, a subnet, or an interface—and assign download and upload limits. This gives immediate, per-target rate control without needing more complex setups. Why this fits best: it directly ties a bandwidth cap to a concrete target, making it the simplest and most approachable way to implement basic rate limiting. Other options don’t provide immediate per-target bandwidth enforcement on their own: a Firewall blocks or allows traffic, Mangle marks packets for later actions, and broader Queues approaches (like a Queue Tree) handle more advanced queuing and shaping but aren’t as simple or targeted for basic per-user, per-subnet, or per-interface limits.

The mechanism being tested is how to apply straightforward bandwidth limits to specific targets like a user, subnet, or interface. Simple Queue is designed for exactly that: you create a queue for a target—whether a single IP, a subnet, or an interface—and assign download and upload limits. This gives immediate, per-target rate control without needing more complex setups.

Why this fits best: it directly ties a bandwidth cap to a concrete target, making it the simplest and most approachable way to implement basic rate limiting. Other options don’t provide immediate per-target bandwidth enforcement on their own: a Firewall blocks or allows traffic, Mangle marks packets for later actions, and broader Queues approaches (like a Queue Tree) handle more advanced queuing and shaping but aren’t as simple or targeted for basic per-user, per-subnet, or per-interface limits.