A company has HPE Aruba Networking infrastructure devices. The devices authenticate clients to HPE Aruba Networking ClearPass Policy Manager (CPPM). You want CPPM to track information about clients…

Question

Options

• ALogging with CPPM configured as a Syslog server.
• BDynamic authorization enabled in the RADIUS settings for CPPM.
• CRADIUS accounting to CPPM, including interim updates.
• DAn IF-MAP interface with CPPM as the destination.

• A
  2% (1)
• B
  7% (3)
• C
  89% (40)
• D
  2% (1)

Explanation

RADIUS accounting is the protocol designed specifically for session tracking - when a client connects, the network device sends an Accounting-Start record to CPPM containing the client's IP address, and periodic Interim-Update records report cumulative bytes sent/received, giving CPPM exactly the bandwidth utilization data it needs.

A is wrong because Syslog delivers unstructured log messages - CPPM can receive them, but Syslog has no standardized format for session stats or bandwidth counters, making it unreliable for client tracking.

B is wrong because Dynamic Authorization (CoA/Disconnect) is the reverse flow - it lets CPPM push policy changes to the network device mid-session. It doesn't cause devices to report client data back to CPPM.

D is wrong because IF-MAP is a metadata-sharing protocol used to propagate identity/context between heterogeneous security systems (e.g., firewalls, IDS). It isn't a mechanism for network devices to report per-client session statistics.

Memory tip: Think of RADIUS Accounting like a taxi meter - Start means the ride began (IP captured), Interim updates tick the fare as data flows (bandwidth tracked), and Stop means the ride ended. RADIUS authentication only checks the passenger's ID at the door; accounting is what actually runs the meter.

No community discussion yet for this question.