WLAN Interworking and Application Scenarios
Domain 8 connects the WLAN to the wired network and to cloud, IoT and location services. The exam tests whether you can place VLANs, gateways and tunnels correctly and recognize cloud dependencies.
Wired integration
A typical design separates the AP management VLAN from service VLANs. The AP management VLAN needs DHCP and a route to the AC; service VLANs carry client traffic. With tunnel forwarding, client traffic is encapsulated to the AC; with local forwarding, it exits at the AP and the wired network must carry those VLANs. DHCP relay and gateway placement must match the forwarding mode.
CloudCampus and IoT
CloudCampus moves management to a cloud controller such as iMaster NCE-Campus. APs need Internet access, DNS and a registration/authentication path; local survivability should be considered. IoT radios or modules (BLE, Zigbee, or integrated IoT) add devices but also power, spectrum and security planning.
Location services
Wi-Fi location uses RSSI fingerprinting or trilateration; BLE adds beacon-based proximity. Accuracy depends on AP density, survey quality and interference.
Worked example: an AP uses management VLAN 100 and service VLANs 200 (employee) and 300 (guest). The switch trunk to the AC allows all three; DHCP relay for 200/300 points to the core. If local forwarding is used, the AP interface must tag 200/300 and the upstream must permit them.
Traps: blocking the management VLAN at the firewall; forgetting DNS for cloud APs; assuming tunnel forwarding needs no service VLAN on the wired side; expecting accurate location from a single AP.