A residence-hall network must profile wireless IoT sensors before they reach the building-automation VLAN. The sensors always request their address with DHCP and include a vendor class identifier and a parameter request list, but they generate no HTTP sessions, expose no SNMP service, and drop all active scans. Which ISE profiling probe supplies the attributes that identify these sensors?

The DHCP probe is correct because the sensors request addresses through DHCP and include both a vendor class identifier and a parameter request list. ISE can inspect those DHCP fields and use them as profiling attributes, without requiring application traffic, a management service, or an active scan. The RADIUS probe is a legitimate profiling source when endpoint authentication or session accounting is available, but the scenario establishes no RADIUS exchange; those attributes therefore cannot be assumed to identify these sensors. The DNS probe can support passive profiling when an endpoint’s DNS activity provides useful evidence, but DNS records do not expose the DHCP vendor class identifier or parameter request list asked about here. The NetFlow probe can passively classify devices from observed flow metadata and avoids active scanning, but flow records do not carry the DHCP options needed for this identification. Exam caveat: several ISE probes may contribute evidence for a profile, so distinguish the probe that can supply the named attributes from other probes that may provide supplementary clues. Practical check: inspect an endpoint’s DHCP request or ISE profiling details and confirm that the vendor class identifier and parameter request list are actually present and mapped to the expected profiling rules.