A company wants you to integrate HPE Aruba Networking ClearPass Policy Manager (CPPM) with HPE Aruba Networking ClearPass Device Insight (CPDI). What is one aspect of the integration that you should…

Question

Options

• ACPPM no longer supports any Device Profiler features and relies on CPDI for this profile
• BCPDI must be configured as an audit server on CPPM for the integration to be successful.
• CCPDI must have security analysis disabled on it for the integration to be successful.
• DCPPM can submit profile information to CPDI, but if CPDI derives a different classification, CPDI

• A
  3% (1)
• B
  7% (2)
• C
  13% (4)
• D
  77% (23)

Explanation

Option D is correct because it accurately describes a key behavioral aspect of the CPPM-CPDI integration: CPPM can contribute its own device profile data to CPDI, but CPDI's AI/ML-driven classification takes precedence - meaning if CPDI derives a different conclusion about a device's identity, CPDI's classification wins. This is by design, as CPDI is the more advanced profiling engine in the solution stack.

Why the distractors are wrong:

• A is false - CPPM retains its own built-in Device Profiler capabilities even when CPDI is integrated; the two coexist rather than one replacing the other.
• B is false - CPDI is not configured as an audit server; audit servers in CPPM are separate components (e.g., vulnerability scanners like Nessus), not device intelligence platforms.
• C is false - security analysis is a core value-add of CPDI, so disabling it would undermine the entire purpose of the integration.

Memory tip: Think of CPDI as the "senior analyst" - CPPM can hand over its notes, but when CPDI reaches a different conclusion, CPDI has the final word. The direction of authority flows toward CPDI, not back to CPPM.

No community discussion yet for this question.