A customer wants to connect a device to an autonomous Cisco AP configured as a WGB. The WGB is configured properly: however, it fails to associate to a CAPWAP-enabled AP. Which change must be applied

Question

Options

• AEnable Aironet IE.
• BEnable passive client.
• CDisable AAA override.
• DDisable FlexConnect local switching.

• A
  73% (19)
• B
  15% (4)
• C
  4% (1)
• D
  8% (2)

Explanation

WGB Association with CAPWAP-Enabled AP

Enabling Aironet IE (Information Elements) is required because a Workgroup Bridge (WGB) relies on Cisco proprietary Aironet IEs to properly communicate and associate with a CAPWAP-enabled access point - without this, the WGB cannot complete the association process, as these IEs carry device-specific capability information that the infrastructure AP needs to recognize the WGB.

Why the distractors are wrong:

• B (Passive Client): This feature helps with clients that don't send DHCP requests or ARP broadcasts, which is unrelated to WGB association failures.
• C (AAA Override): This controls whether RADIUS attributes can override WLAN settings for individual clients - it has no bearing on WGB-to-AP association.
• D (Disable FlexConnect Local Switching): FlexConnect settings apply to branch office AP deployments and don't affect a WGB's ability to associate with a CAPWAP AP.

Memory Tip: Think of Aironet IE = Identity Card for Cisco devices - just as a WGB needs to "show its Cisco ID" to get into the network, Aironet IE is what allows Cisco proprietary devices like WGBs to be recognized and permitted to associate. If the WGB can't "prove it's Cisco," the door stays closed.

No community discussion yet for this question.