* MAC Spoofing Detection with Endpoint Conflict:
* When two devices attempt to use the same MAC address, ClearPass identifies a Conflict state in the Endpoints Repository.
* This condition can be used to detect and quarantine clients that spoof legitimate devices.
* Option D: Correct. The Conflict EQUALS true condition identifies devices with duplicate MAC addresses.
* Option A: Incorrect. Endpoint compliance checks posture, not MAC spoofing.
* Option B: Incorrect. Device Insight Tags are used for profiling but do not identify conflicts.
* Option C: Incorrect. Compromised devices relate to security incidents, not MAC address conflicts.

When a switch port connects to a wireless AP that bridges multiple client VLANs, best practice is to:
* Keep the VLAN/trunking configuration on the interface (not forced by the role), so that both VLAN 18 (AP management) and VLAN 12 (clients) are supported.
* Enable trust of DSCP on the AP uplink so that QoS markings from the AP (voice, real-time traffic) are honored end-to-end, instead of being remarked or reset at the switch. Aruba wired-access and campus deployment guides repeatedly recommend trusting DSCP on AP uplinks so that WMM/802.11e markings are preserved.
Option D ("Access VLAN 18 with no support for VLAN 12") would break the design because the AP needs to carry client VLAN 12 across its uplink. Option C (auth-mode client-mode) is about how many supplicants per port are authenticated; it is not the key "recommended" setting in this scenario, and Aruba designs typically focus QoS for AP uplinks via trust settings.
Therefore, the recommended role setting here is to trust DSCP on the AP's authenticated role # Option B.

The preferred method for assigning clients to a role on the AOS firewall is to configure HPE Aruba Networking ClearPass Policy Manager (CPPM) to assign the role using a RADIUS enforcement profile with an Aruba-User-Role VSA (Vendor-Specific Attribute). This method allows ClearPass to dynamically assign the appropriate user roles to clients during the authentication process, ensuring that role-based access policies are consistently enforced across the network.
Reference: Aruba ClearPass documentation and RADIUS configuration guides provide detailed instructions on setting up RADIUS enforcement profiles and using the Aruba-User-Role VSA for role assignment.

To capture only the traffic sent in the mirroring session between an AOS-CX switch and a management station running Wireshark, you should apply a capture filter that isolates the specific traffic of interest. In this case, using the filter udp port 5555 will capture the traffic associated with the mirroring session. This is because AOS-CX switches typically use UDP port 5555 for mirrored traffic, ensuring that only the relevant mirrored packets are captured and excluding other traffic generated by the management station.
Reference: Aruba's AOS-CX documentation and network management guides detail the configuration and monitoring of traffic mirroring sessions, including the use of specific ports for mirrored traffic.

After installing an HPE Aruba Networking Network Analytic Engine (NAE) script on an AOS-CX switch, the additional step required to start the monitoring is to create an agent from the script. The agent is responsible for executing the script and collecting the monitoring data as defined by the script parameters.
1.Script Installation: Installing the script provides the logic and parameters for monitoring.
2.Agent Creation: Creating an agent from the script activates the monitoring process, allowing the NAE to begin tracking the specified function.
3.Operational Step: This step ensures that the monitoring logic is applied and the data collection starts as per the script's configuration.
Reference: Aruba AOS-CX documentation and Network Analytics Engine guides outline the process of script installation and the necessity of creating an agent to activate monitoring.