What does the LAP send when multiple WLCs respond to the CISCO_CAPWAP- CONTROLLER.localdomain hostname during the CAPWAP discovery and join process?

Question

Options

• Abroadcast discover request
• Bjoin request to all the WLCs
• Cunicast discovery request to each WLC
• DUnicast discovery request to the first WLS that resolves the domain name

• A
  3% (2)
• B
  2% (1)
• C
  88% (53)
• D
  7% (4)

Explanation

CAPWAP Discovery Process Explanation

When multiple WLCs respond to the CISCO_CAPWAP-CONTROLLER.localdomain DNS hostname, the LAP (Lightweight Access Point) sends a unicast discovery request to each WLC that responded, allowing it to evaluate all available controllers before selecting one to join. This ensures the LAP can gather information (such as load and priority) from every responding WLC to make an informed join decision.

Why the distractors are wrong:

• A (broadcast discover request): Broadcasts are used in the initial discovery phase, not after DNS resolution has already identified specific WLC IP addresses.
• B (join request to all WLCs): The LAP sends discovery requests first; a join request is only sent to the single, selected WLC after the discovery phase is complete.
• D (unicast to first WLC only): The LAP does not stop at the first responding WLC - it contacts all resolved controllers to compare options before committing.

Memory Tip: Think of it like job hunting - you get a list of employers (DNS returns multiple WLC IPs), you contact each one individually (unicast discovery) to gather offers, and then you accept just one job (unicast join request). Discovery = shop around; Join = commit to one.

No community discussion yet for this question.