When using the 802.1X/EAP framework for authentication in 802.11 WLANs, why is the 802.1X Controlled Port still blocked after the 802.1X/EAP framework has completed successfully?

When using the 802.1X/EAP framework for authentication in 802.11 WLANs, why is the 802.1X Controlled Port still blocked after the 802.1X/EAP framework has completed successfully?
A . The 802.1X Controlled Port is always blocked, but the Uncontrolled Port opens after the EAP authentication process completes.
B . The 802.1X Controlled Port remains blocked until an IP address is requested and accepted by the Supplicant.
C . The 4-Way Handshake must be performed before the 802.1X Controlled Port changes to the unblocked state.
D . The 802.1X Controlled Port is blocked until Vender Specific Attributes (VSAs) are exchanged inside a RADIUS packet between the Authenticator and Authentication Server.

View Answer

Answer: C