An engineer is optimizing the wireless network. In order to prevent non-critical services from occupying too much network resources, he turns on the QoS function based on the application protocol…

Question

Options

• AAP directly connected to the upper switch
• BAP
• CUser gateway equipment
• DWAC

• A
  8% (4)
• B
  6% (3)
• C
  83% (40)
• D
  2% (1)

Explanation

In tunnel forwarding mode, all wireless user traffic is encapsulated inside CAPWAP tunnels from the AP to the WAC - meaning the application-layer payload is hidden inside those tunnels and cannot be meaningfully inspected by intermediate devices. The traffic only emerges as fully readable application data at the user gateway, making it the correct and only viable point to apply QoS policies based on application protocol (which requires deep packet inspection of the actual payload).

Why the distractors are wrong:

• A (Upper switch): The switch handles CAPWAP-encapsulated frames, not raw user traffic - it cannot see application protocols.
• B (AP): The AP's role in tunnel mode is to encapsulate and forward, not to inspect and enforce application-layer QoS; APs are radio management devices, not policy enforcement points.
• D (WAC): While the WAC decapsulates CAPWAP tunnels, it then forwards traffic upstream - the WAC is responsible for wireless control-plane functions, and in this architecture the application QoS policy is applied at the gateway where all decapsulated traffic converges and exits to the network.

Memory tip: Think "Tunnel = Traffic is Tucked away." In tunnel forwarding, user packets stay hidden inside CAPWAP until they reach the user gateway - so the gateway is the first and only place where application protocols are visible for QoS inspection.

No community discussion yet for this question.