Question 410
At Riverside Building, an access template accidentally treats RADIUS reject like a server timeout. Which preventive control is most relevant to this scenario over time?
Explanation
Correct Answer
For Riverside Building, the decisive mechanism is Unauthorized fail-open behavior. Authentication rejection is not the same as RADIUS server unavailability. Audit fallback policy to avoid conflating rejected credentials with unavailable servers is an enduring limitation on the operational risk, not simply a one-time passing test.
Incorrect Answers
This is relevant to Wired 802.1X port access, where 802.1X authorizes port traffic through EAPOL and the authentication server decision In the Riverside Building case, A precaution for another failure mode is not the enduring boundary needed here. The specific mechanism is authentication rejection is not the same as RADIUS server unavailability
This is relevant to Supplicant reauthentication intervals, where wired reauthentication intervals can affect session continuity if handshake timing is inadequate In the Riverside Building case, A precaution for another failure mode is not the enduring boundary needed here. The specific mechanism is authentication rejection is not the same as RADIUS server unavailability
This is relevant to RADIUS authorization timeout, where authentication server reachability and retry order influence network-admission decisions In the Riverside Building case, A precaution for another failure mode is not the enduring boundary needed here. The specific mechanism is authentication rejection is not the same as RADIUS server unavailability