A town hall branch will use cloud-managed APs. A volunteer suggests skipping switch VLAN and PoE work because 'the cloud handles everything.' What should the technician explain?
Select an answer to reveal the explanation.
Short Explanation
Cloud is the remote brain, not a magic wireless umbilical. The AP still sits on a cable that needs the right VLAN and PoE juice. Dashboard presence does not replace closet work.
Full Explanation
When a town hall branch will use cloud-managed APs and a volunteer suggests skipping switch VLAN and PoE work because the cloud handles everything, the technician must explain that cloud-managed APs still need correct local switch VLANs and PoE (or equivalent power) when the design uses wired backhaul. Cloud management moves the controller function to a hosted dashboard; it does not remove Layer-2 switching, tagging, or power delivery at the branch closet. Municipal installs still require proper Ethernet infrastructure under the AP.
Cloud management does not remove the need for Ethernet cabling to a wired-backhaul AP. Cloud APs do not communicate only over cellular such that LAN switching never matters in a wired design. VLAN tagging is not obsolete merely because an AP appears in a cloud dashboard; wrong VLANs still break management or client segmentation.
Exam caveat: cloud equals management plane location—local switching and PoE remain on-site responsibilities. Operational check: verify the branch switch port has correct data/management VLAN tagging and PoE budget for the AP, claim the AP in the cloud tenant, and confirm it stays online serving the town-hall SSIDs. Include switch port descriptions and PoE budget notes in the branch turn-up checklist beside the cloud claim steps.