Which WLC Profiling Mechanism Sends Device Data to Cisco ISE?
A network engineer is configuring a Cisco WLC in order to find out more information about the devices that are connecting. This information must be sent to Cisco ISE to be used in authorization policies. Which profiling mechanism must be configured in the Cisco WLC to accomplish this task?
Community Votes
75% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests the distinction between WLC-side Device Sensor protocols and ISE-side probes; the trap is choosing SNMP because ISE can query the WLC via SNMP, but the question asks what is configured on the WLC itself.
The Cisco WLC Device Sensor must be configured with DHCP to forward client attributes to Cisco ISE for profiling and authorization. This page confirms DHCP (D) as the required mechanism, explains why SNMP is an ISE-side probe, and reviews community voting.
Learners pick SNMP (A) because ISE's SNMP probe can collect data from the WLC, but SNMP is configured on ISE, not on the WLC, and the WLC Device Sensor forwards DHCP (and RADIUS) attributes for profiling.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The WLC Device Sensor feature is designed to snoop DHCP and RADIUS packets from wireless clients and forward the extracted attributes to Cisco ISE. ISE then uses those DHCP attributes—hostname, device class, OS, vendor—to build endpoint profiles that feed authorization policies. In the 300-715 exam doctrine, when the task asks what is configured on the WLC itself to supply profiling data, DHCP is the standard answer. The community comment from arashdehghan reinforces this, noting the WLC Device Sensor "only supports DHCP and RADIUS traffic."
Why the Other Options Are Wrong
Option A (SNMP) is an ISE-side probe: ISE queries the WLC via SNMP to collect extra attributes, but the SNMP probe is configured on ISE, not as a WLC device sensor mechanism. Although Pages argued "ISE will use SNMP to query the wireless controller for specific attributes," that describes a probe on ISE rather than a setting on the WLC, so it does not satisfy the question. Option B (CDP) is a neighbor-discovery protocol; while some WLC releases can include CDP/LLDP in device sensor output, it is not the primary profiling mechanism that ISE expects for DHCP-derived endpoint attributes and is not the correct exam answer here. Option C (DNS) is another ISE probe (reverse DNS lookup) used for name resolution, not something you configure on the WLC to send profiling data.
Community Comment Notes
Commenters overwhelmingly selected D (75 votes vs. 25 for A), with 4004aa3 explicitly stating that "if question about configuring probe on Cisco ISE than both A and D is valid answer" but because the question asks what is configured on the WLC, D is correct. arashdehghan explained that Device Sensor on the WLC handles this and only supports DHCP and RADIUS traffic. ZoneHacker simply affirmed "Answer D is the right answer." Pages' SNMP answer reflects a common confusion between ISE probes and WLC-side sensor configuration, which the other commenters correct.
Official Reference
Exam Strategy
Separate the roles: ISE-side probes (SNMP, DNS, NetFlow, NMAP) versus WLC-side device sensor protocols (DHCP, RADIUS). Read the question stem for the phrase 'configured in the Cisco WLC' — that points to DHCP, not SNMP. When in doubt, remember ISE's profiling guide pairs WLC device sensor with DHCP attributes.
Frequently Asked Questions
Why is SNMP not the correct WLC profiling mechanism here?
SNMP is an ISE-side probe that queries the WLC for attributes; it is not a Device Sensor protocol configured on the WLC to push client data to ISE.
What does the WLC Device Sensor send to Cisco ISE?
It forwards DHCP and RADIUS attributes such as hostname, device type, and OS so ISE can build endpoint profiles for authorization policies.