A parks department is replacing controller-based APs with cloud-managed APs in recreation centers. Why must the deployment checklist change rather than reuse the old controller discovery steps unchanged?
Select an answer to reveal the explanation.
Short Explanation
Controller discovery is not cloud claim-and-adopt. If the parks team runs yesterday's checklist on today's cloud APs, adoption fails and nobody knows why. Match the checklist to the architecture.
Full Explanation
WLAN architectures differ in how APs discover controllers, claim into cloud tenants, or boot autonomously. Deployment checklists must capture the correct certificates, DHCP options, firewall allowances, and adoption workflows for the chosen architecture. Reusing controller-only steps for cloud APs (or the reverse) causes failed onboarding and incomplete installs even when RF placement is correct.