Drag and Drop Question Match the ClearPass system description to the best term Options are used only once. Answer:

Question

Exhibit

Answer Area

Explanation

ClearPass Component Matching - Explained

This question tests knowledge of the Aruba ClearPass security platform's distinct modules. Each module has a single, well-defined role.

1. ClearPass Insight → "provides multiple customizable reports and in-depth information about each of the other modules"

Why: "Insight" is purely an analytics and reporting engine. The name itself signals visibility. It aggregates data from all other ClearPass modules and presents dashboards, trends, and audit reports. It does not enforce policy or configure devices - it only reports on them.

Common mistake: Confusing Insight with Policy Manager for integration/APIs. Policy Manager is the hub for external integration; Insight is purely internal visibility.

2. ClearPass Onboard → "provides an intuitive way to securely assign an individual client certificate to each device"

Why: "Onboard" handles device provisioning and certificate enrollment. When a user brings a personal device (BYOD), Onboard guides them through self-service certificate issuance so the device can authenticate securely. The key technical concept is per-device X.509 certificates - not passwords.

Common mistake: Confusing Onboard with OnGuard. Onboard gets devices onto the network with credentials; OnGuard checks device health after it's there.

3. ClearPass OnGuard → "can provide posturing to validate the security status of devices on your wired, wireless and VPN networks"

Why: "OnGuard" is a posture assessment (NAC health check) agent. It runs on endpoints and verifies security compliance - antivirus up-to-date, firewall enabled, patches applied, etc. - across all three network types (wired, wireless, VPN). This breadth across connection types is a distinguishing detail in the description.

Common mistake: Thinking OnGuard handles certificate provisioning (that's Onboard) or device fingerprinting (that's Profiler).

4. ClearPass Policy Manager → "has the ability to integrate with external systems through APIs or HTTP/REST calls"

Why: Policy Manager (CPPM) is the core AAA/policy engine and the central hub of the ClearPass platform. As the integration point for the entire ecosystem, it exposes REST APIs and can make HTTP calls to external systems (firewalls, MDM, SIEM, etc.) to enforce dynamic policies. All other modules feed into or are orchestrated by CPPM.

Common mistake: Students sometimes assign this to Insight (thinking "integration" means reporting). The distinguishing phrase is APIs/REST calls - that's active system integration, not reporting. Also don't confuse "external systems" with Profiler's passive data collection.

5. ClearPass Profiler → "gathers endpoint context from passively received data to fingerprint devices"

Why: Profiler performs passive device fingerprinting. It listens to network traffic (DHCP, HTTP user-agents, SNMP, etc.) without actively probing devices, building a profile of what each device is (iPhone, Windows laptop, IoT sensor). The word "passively" in the description is the critical technical differentiator.

Common mistake: Confusing Profiler with OnGuard. OnGuard actively runs on a device to check its health. Profiler observes network traffic without touching the device - it's agentless and passive.

Quick Reference Table

The exam answer hinges on recognizing one unique keyword per module - passive (Profiler), certificate (Onboard), posturing (OnGuard), REST/API (Policy Manager), reports (Insight).

No community discussion yet for this question.