Looking at the configuration of the switch, what could be the possible issue?

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

aaa server radius dynamic-author

host 161.1.7.14 server key cisco

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-time 0

dot1x system-auth-control

interface g1/0/9

switchport mode access

ip device tracking maximum 10

authentication host-mode multi-auth

authentication port-control auto

dot1x pae authenticator

radius-server host 161.1.7.14 key cisco

radius-server timeout 60

line con 0

login authentication NO_AUTH

line vty 0 4

login authentication vty

A customer has opened a case with Cisco TAC reporting an issue that one of the Windows client supposed to login to the network using MAB is no longer able to access any allowed resources.

Looking at the configuration of the switch, what could be the possible issue?
A . there is an issue with DHCP pool configuration
B . there is an issue with CoA configuration
C . AAA authorization is incorrectly configured
D . incorrect CTS configuration on the switch
E . dot1x should be globally disabled for the MAB to work
F . the switch is properly configured and the issue is on the radius server
G . authentication port g1/0/9 is not configured to perform mab

View Answer

Answer: G