What happens when a client successfully authenticates but does not match any Enforcement Policy rules?
no role is applied to the device
logon profile is applied to the device
default Enforcement profile is applied
guest rule is applied to the device
default rule is applied to the device
Correct answer: C
Explanation:
The first time a device connects, it's allowed on in a limited state (session timeout is a low value and DHCP is allowed) because it doesn't match any Enforcement policy rules based on Endpoint Category. The default enforcement profile is used. Reference: http://community.arubanetworks.com/t5/Security/MAC-Auth-Service-for-AP-s-Printers-Etc/td-p/243252
The first time a device connects, it's allowed on in a limited state (session timeout is a low value and DHCP is allowed) because it doesn't match any Enforcement policy rules based on Endpoint Category. The default enforcement profile is used.
For Active Directory, the bind DN can also be in the administrator@domain format (for example, [email protected]). Reference http://www.arubanetworks.com/techdocs/ClearPass/Aruba_CPPMOnlineHelp/Content/CPPM_UserGuide/Auth/AuthSource_GenericLDAP.htm
For Active Directory, the bind DN can also be in the administrator@domain format (for example, [email protected]).