Looking at the configuration what may cause the MAB authentication to fail for a supplicant?

Refer to the exhibit.

aaa authentication login default group radius

aaa authentication login NO_AUTH none

aaa authentication login vty local

aaa authentication dot1x default group radius

aaa authorization network default group radius

aaa accounting update newinfo

aaa accounting dot1x default start-stop group radius

!

ip dhcp excluded-address 60.1.1.11

ip dhcp excluded-address 60.1.1.2

!

ip dhcp pool mabpc-pool

network 60.1.1.0 255.255.255.0

default-router 60.1.1.2

!

cts sxp enable

cts sxp default source-ip 10.9.31.22

cts sxp default password ccie

cts sxp connection peer 10.9.31.1 password default mode peer listener hold-time0

!

dot1x system-auth-control

!

interface GigabitEthernet1/0/9

switchport mode access

ip device tracking maximum 10

authentication host-mode multi-auth

authentication port-control auto

mab

!

radius-server host 161.1.7.14 key cisco

radius-server timeout 60

!

interface VLAN10

ip address 10.9.31.22 255.255.255.0

!

interface Vlan50

no ip address

!

interface Vlan60

ip address 60.1.1.2 255.255.255.0

!

interface Vlan150

ip address 150.1.7.2.255.255.255.0

Looking at the configuration what may cause the MAB authentication to fail for a supplicant?
A . There is an issue with the DHCP pool configuration
B . The VLAN configuration is missing on the authentication port
C . Incorrect CTS configuration on the switch
D . AAA authorization is incorrectly configured on the switch.
E . CoA configuration is missing
F . Dot1x should be globally disabled for MAB to work
G . Switch configuration is properly configured and the issue is on the Radius server.

View Answer

Answer: G