A company wants you to create a custom device fingerprint on CPPM with rules for profiling a group of specialized devices. What is one requirement?

Question

Options

• AConnecting a known device of this type and getting it discovered in CPPM's Endpoints Repository.
• BEnabling HPE Aruba Networking ClearPass Device Insight integration with the correct Data
• CPre-defining the desired attributes and rules in an XML format file.
• DDisabling the "Automatically download Endpoint Profiler Fingerprints" feature in cluster-wide

• A
  76% (22)
• B
  3% (1)
• C
  14% (4)
• D
  7% (2)

Explanation

To create a custom device fingerprint in ClearPass Policy Manager (CPPM), you must first connect a known device of that type so CPPM can discover it and populate the Endpoints Repository with its real attributes (MAC OUI, DHCP fingerprint, HTTP user-agent, etc.) - you need actual captured data to build rules against. Option B is wrong because ClearPass Device Insight is a separate, optional integration for enhanced AI-driven profiling, not a requirement for manual custom fingerprints. Option C is incorrect because CPPM's fingerprint rules are configured through the GUI (or via the built-in Fingerprints editor), not by uploading an XML file. Option D is a red herring - disabling automatic fingerprint downloads is unrelated to creating a custom fingerprint and would actually reduce your profiling coverage.

Memory tip: Think "see it to fingerprint it" - CPPM must discover a real device before you can build custom rules around its attributes. No discovered device = no data = no fingerprint.

No community discussion yet for this question.