Wireless architecture appears in CloudNetX because campus designs must account for shared-medium behavior, mobility, and policy consistency across many access points. This episode defines the access point as the radio interface that connects clients to the network and the controller as the component that centralizes configuration, roaming behavior, security policy, and operational visibility across multiple APs. The first paragraph focuses on the division of responsibility, explaining why controller-based designs simplify consistency and improve roaming at scale, while controllerless approaches can work well for smaller sites with simpler requirements. It also introduces wired dependencies that are often overlooked, such as uplink capacity, PoE availability, and proper segmentation, because wireless performance is limited by the backhaul and the policies that govern where wireless clients can go once connected.