A company wants to use HPE Aruba Networking ClearPass Policy Manager (CPPM) to profile Linux devices. You have decided to schedule a subnet scan of the devices' subnets. Which additional step should…

Question

Options

• ASet up SSH accounts on CPPM and map them to the Linux devices' subnets.
• BEnable WMI probing in the cluster-wide parameters.
• CEnable the Data Port in the ClearPass server settings and connect that port to the network.
• DConfigure SNMP in the network device settings for the switches that support the Linux devices.

• A
  2% (1)
• B
  3% (2)
• C
  85% (53)
• D
  10% (6)

Explanation

Enabling the Data Port is the required prerequisite because CPPM uses this dedicated interface - separate from the Management Port - to send active probe traffic during subnet scans. Without enabling it in ClearPass server settings and physically connecting it to the network, the scan engine has no path to reach endpoints on the target subnets, so no profiling data can be collected.

Why the distractors are wrong:

• A (SSH accounts): SSH-based profiling is a separate method for deeper CLI fingerprinting; it is not a prerequisite for scheduling a subnet scan.
• B (WMI probing): WMI is a Windows-only protocol - it has no relevance to profiling Linux devices.
• D (SNMP on switches): SNMP can supplement endpoint profiling via switch polling, but configuring it is not the required step before a subnet scan; the Data Port is.

Memory tip: Think of the Data Port as ClearPass's "scanning antenna" - before it can listen or probe the network, the antenna must be turned on (enabled) and plugged in (connected). No port, no scan.

No community discussion yet for this question.