In the AOS-CX architecture, a Local User Role (LUR) is a logical container that defines the network privileges and connectivity settings for a client once they have been successfully authenticated. Unlike " Downloadable User Roles " (DUR), which are stored on ClearPass, LURs are defined directly in the switch configuration.
VLAN Assignment (Option A): One of the primary functions of a user role is to dynamically assign a client to a specific VLAN. This allows the physical port to remain " colorless " —the port ' s VLAN membership is determined by the identity of the user rather than a static configuration on the interface.
ACL (Access Control List) (Option E): To enforce " Least Privilege " security, LURs allow you to attach an IPv4 or IPv6 ACL directly to the role. This ensures that even if two users are in the same VLAN, their traffic can be filtered differently based on the role they were assigned (e.g., a " Contractor " role might have an ACL blocking access to internal servers, while an " Employee " role does not).
Why other options are incorrect:
Option B: The ClearPass server is part of the global AAA (RADIUS) configuration. It is the destination for authentication requests, not a parameter defined within a specific user role.
Option C: While many CLI commands allow for a description, it is a metadata field for administrative clarity and is not considered a functional " parameter " of network enforcement in the context of the ACP-S exam.
Option D: Authentication methods (like 802.1X or MAC-auth) are the triggers that result in a role being applied. They are configured at the interface or global level, not inside the role itself.
