Question 730
At the Tarnbridge data network services firm, a desktop never enters its assigned VLAN and RADIUS logs contain no request for the affected connection. Which explanation best accounts for the concern?
Explanation
Correct Answer
The problem stems from the fact that missing supplicant EAPOL traffic indicates the authentication flow may not reach RADIUS. A correct solution would capture EAPOL frames on the client-facing switch port before investigating server-side authorization and check that a controlled authentication shows EAPOL exchange at the port and a corresponding RADIUS attempt.
Incorrect Answers
The offered principle is: A rogue ARP sender can impersonate an IP address without changing DHCP lease records. In the source material it is associated with: A rogue ARP sender can impersonate an IP address without changing DHCP lease records. This case has a different controlling cause: Missing supplicant EAPOL traffic indicates the authentication flow may not reach RADIUS. Its keyed mechanism is: Missing supplicant EAPOL traffic indicates the authentication flow may not reach RADIUS.
The offered principle is: Controller discovery and authorization are separate stages of managed provisioning. In the source material it is associated with: Controller discovery and authorization are separate stages of managed provisioning. This case has a different controlling cause: Missing supplicant EAPOL traffic indicates the authentication flow may not reach RADIUS. Its keyed mechanism is: Missing supplicant EAPOL traffic indicates the authentication flow may not reach RADIUS.
Routing decisions depend on active installed routes and reachable next hops. That may occur elsewhere, but the evidence at the Tarnbridge data network services firm instead points to the fact that missing supplicant EAPOL traffic indicates the authentication flow may not reach RADIUS.