Question 140
During a Cisco ISE postchange review, the following is observed: A wireless 802.1X rollout has successful connections but no traceable per-user session-end accounting in ISE when users disconnect. Which architectural fact determines the appropriate fix?
Explanation
Correct Answer
RADIUS authentication exchanges grant access, while accounting records session start, stop, and interim usage events when configured. This behavior directly governs the stated requirement. The recommended action is: Enable supported RADIUS accounting from the controller and confirm the necessary accounting server settings and message path. The acceptance result is: A test wireless session generates a matching accounting start and stop tied to its authenticated identity.
Incorrect Answers
Test SSID and network-device-group conditions in each wireless authorization policy set. The repeat risk here is different: Include CoA reachability and session-identity checks in wireless integration acceptance tests. A directly relevant preventive control is: RADIUS authentication exchanges grant access, while accounting records session start, stop, and interim usage events when configured.
Verify RADIUS source interfaces after controller failover, redundancy, or interface changes. The repeat risk here is different: Include CoA reachability and session-identity checks in wireless integration acceptance tests. A directly relevant preventive control is: RADIUS authentication exchanges grant access, while accounting records session start, stop, and interim usage events when configured.
Include DNS locator and domain connectivity checks in ISE node renumbering. The repeat risk here is different: Include CoA reachability and session-identity checks in wireless integration acceptance tests. A directly relevant preventive control is: RADIUS authentication exchanges grant access, while accounting records session start, stop, and interim usage events when configured.