On which interfaces should traffic policing be applied?

Question

Options

• AConsole interfaces
• BOutgoing interfaces
• CIncoming interfaces
• DLoopback interfaces

• A
  4% (1)
• B
  4% (1)
• C
  91% (21)

Explanation

Traffic policing is applied on incoming interfaces because the goal is to enforce rate limits at the point where traffic enters a network device - dropping or marking excess packets before they consume downstream resources. This is the most efficient place to act, as it prevents overloading internal queues and links before traffic propagates further into the network.

Why the distractors are wrong:

• A (Console): Console interfaces are management ports for device administration, not data-plane interfaces where user traffic flows.
• B (Outgoing): Outgoing interfaces are where traffic shaping (buffering/queuing) is typically applied, not policing. Policing on egress is less common and less effective since the traffic has already traversed the device.
• D (Loopback): Loopback interfaces are logical/virtual interfaces used for routing and management purposes; no real user traffic enters or exits through them.

Memory tip: Think "Policing = Port of entry" - just like a bouncer checks IDs at the door (incoming), not on the way out.

No community discussion yet for this question.