Cognitive Campus Workspaces: Assurance-Driven User Experience
Core concepts
A cognitive campus shifts operations from device-centric to experience-centric. Candidates must understand the telemetry foundation: streaming telemetry from switches and access points, client onboarding analytics, and AI/ML-driven baselining that flags anomalies rather than static thresholds. Key constructs include fabric-enabled campus (VXLAN overlay with a border and edge nodes), unified policy that follows the user rather than the port, and identity integration (802.1X, MAB, guest portals) feeding a single policy engine. Wireless adds RF concepts: channel planning, roaming (802.11r/k/v), and the difference between coverage problems and capacity problems. Workspace experience also covers IoT onboarding, profiling, and segmentation of unmanaged devices. Understand how assurance scores are computed from onboarding time, connectivity failures, and application experience, and how that data drives automated remediation.
Traps
Questions often imply AI replaces configuration - it augments visibility and suggests action; human-approved intent still governs. Distinguish coverage (signal present) from capacity (airtime and client count). Another trap: assuming a fabric is required for all features; many assurance capabilities work on non-fabric deployments. Watch for policy that is applied per-port instead of per-identity, which breaks mobility.
Worked example
Users report slow roaming between floors. Check: is 802.11r enabled on both controllers? Are the same SSID/VLAN/policy mapped on both? Rule of thumb: roam failures are usually policy or key-caching mismatches, not RF - verify identity and VLAN consistency before touching power levels.
Rule of thumb
If the question describes a user symptom, answer with the telemetry or policy source that would explain it.