Difficulty: Medium
Correct Answer: Controller and Access point
Explanation:
Introduction / Context:
Enterprise Cisco WLANs commonly use lightweight access points (LAPs) joined to a Wireless LAN Controller (WLC). In a mesh deployment, APs may function as mesh root or mesh nodes, but centralized control remains central to Cisco's Unified Wireless architecture. Understanding which components are required versus optional avoids unnecessary purchases.
Given Data / Assumptions:
Concept / Approach:
A lightweight AP needs to join a WLC to operate in Unified mode. Mesh roles (root and mesh APs) still register to the controller via CAPWAP and rely on WLC for control-plane policy, client state, and mobility. Therefore, at minimum you need a WLC and compatible mesh-capable APs. Management platforms like WCS/Prime add convenience but are not strictly required for functionality. A standalone bridge may be used in specific point-to-point links, but it is not an absolute requirement for Unified mesh WLAN.
Step-by-Step Solution:
List possible components: WCS/Prime (management), WLC (control), LAPs (radios), optional bridges.Identify mandatory control-plane: WLC.Identify mandatory RF endpoints: Access points.Select “Controller and Access point.”
Verification / Alternative check:
Controller configuration guides show mesh AP registration and operation dependent on an available WLC; without a controller, LAPs cannot serve clients in Unified mode.
Why Other Options Are Wrong:
Common Pitfalls:
Confusing autonomous (controller-less) APs with Unified (controller-based) deployments; the mesh feature discussed here refers to the latter.
Final Answer:
Controller and Access point
Discussion & Comments