For ClearPass to periodically query Microsoft Intune / Endpoint Manager for device attributes (compliance, owner, OS, etc.), you must configure Intune as an authentication source in Policy Manager. The ClearPass–Intune integration is implemented through an API-based auth source which CPPM polls on a schedule; it is not done via Guest extensions or syslog/event sources.

Aruba’s Intune integration guides describe configuring a “Microsoft Intune” (or “Endpoint Manager”) authentication source in ClearPass and supplying the Azure app registration details so CPPM can poll Intune via Microsoft Graph.

Option A is incorrect: the Intune integration is not a ClearPass Guest extension.

Option B is insufficient: adding dictionaries only defines attributes; it does not enable scheduled polling.

Option D is incorrect: Intune is not used as a syslog/event source for this use case; ClearPass initiates the polling via the authentication source.

Therefore, the correct configuration step is: Create an Intune authentication source on CPPM (Option C).

In HPE Aruba Networking ClearPass Device Insight (CPDI), a device with a Risk Score of 90 indicates that the posture is unhealthy, and CPDI has detected at least one vulnerability on the device. The risk score is a reflection of the device's security posture and detected vulnerabilities. A high risk score, such as 90, typically signifies significant security concerns, including the presence of vulnerabilities that could be exploited, thereby categorizing the device as a high-risk asset within the network.

Policy Analysis:

Rule Evaluation Order: Rules are applied in sequential order until a match is found.

Key Points:

DHCP traffic (UDP 67) is permitted.

DNS traffic (UDP 53) is permitted.

Traffic to 10.5.5.0/24 is explicitly denied.

HTTP traffic (TCP 80) is allowed only to 10.5.0.0/16.

HTTPS traffic (TCP 443) is allowed only to 10.5.0.0/16.

All other traffic to 10.5.0.0/16 is denied.

Any other traffic not matching the above rules is permitted.

Scenario Analysis:

The client IP 10.2.2.2 does not fall within the 10.5.0.0/16 subnet.

Rule 3 denies traffic to 10.5.5.5, regardless of the source IP.

Option A: Correct. HTTPS traffic to 10.5.5.5 is explicitly denied by Rule 3.

Option B: Incorrect. Traffic to 203.0.113.12 is permitted due to the final "permit any" rule.

Option C: Incorrect. The client (10.2.2.2) does not belong to the subnet 10.5.0.0/16, so traffic to 10.5.3.3 is not permitted by Rule 5.

Option D: Incorrect. HTTP traffic to 198.51.100.12 is allowed by the last "permit any" rule.