Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

HP Exam HPE6-A84 Topic 2 Question 15 Discussion

Actual exam question for HP's HPE6-A84 exam
Question #: 15
Topic #: 2
[All HPE6-A84 Questions]

You are setting up Aruba ClearPass Policy Manager (CPPM) to enforce EAP-TLS authentication with Active Directory as the authentication source. The company wants to prevent users with disabled accounts from connecting even if those users still have valid certificates.

As the first part of meeting these criteria, what should you do to enable CPPM to determine where accounts are enabled in AD or not?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Ilona
10 days ago
D? Really? I don't know, that seems like a bit of a workaround. Why not just go with the direct AD integration in the first place?
upvoted 0 times
...
An
12 days ago
I don't know, guys. I'm kinda leaning towards D - the Microsoft AD extension in ClearPass Guest. That might be the easiest way to integrate with AD.
upvoted 0 times
...
Kathryn
13 days ago
You know, B might be a good option too. OCSP is designed for this kind of thing. Though it might be a bit more complex to set up.
upvoted 0 times
...
Johnna
14 days ago
Yeah, C does sound the most logical. But what about B - using OCSP? Wouldn't that also work by querying the domain controller directly?
upvoted 0 times
...
Gladys
16 days ago
Hmm, I'm leaning towards C - adding a custom attribute for userAccountControl in the AD authentication source. That seems like the most direct way to check the account status.
upvoted 0 times
...
Latonia
17 days ago
Whoa, this question is tricky! We need to figure out how to get CPPM to check the AD account status, but it's not straightforward. I'm going to have to think this through.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77