A county WLAN uses controller-based APs downtown and cloud-managed APs at rural branches. When staging hardware for a new branch clinic, what selection awareness should the technician apply?
Select an answer to reveal the explanation.
Short Explanation
Hybrid campuses are like mixed fleets—sedans downtown, trucks at the farms. You do not drop a downtown controller AP into a cloud-only clinic and hope. Pick the type the site design actually calls for.
Full Explanation
A county WLAN that uses controller-based APs downtown and cloud-managed APs at rural branches requires selecting the AP management type specified for that site—cloud-managed for a new branch clinic—rather than assuming one campus-wide architecture. Mixed architectures are common in municipal deployments; staging must match the site's management plane. Choosing the wrong AP type causes join failures and wasted truck rolls to rural clinics.
Leftover downtown lightweight APs will not simply join the branch cloud tenant without conversion or correct cloud-capable hardware. Cloud APs and controller-based APs are not identical with only mounting color differing. Rural branches must not be forced onto the downtown controller when WAN or architecture standards specify cloud management for that site.
Exam caveat: read the site architecture from the design—do not assume one management model citywide. Operational check: stage a cloud-managed AP model approved for clinics, claim it into the branch cloud tenant, confirm SSIDs match rural policy, and leave downtown controller-based SKUs in downtown inventory. Maintain separate staging images or templates for downtown controller APs and rural cloud APs to prevent cross-site mix-ups.