Cyber Monday 2024! 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 10 Question 14 Discussion

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

You want to use Device Insight tags as conditions within CPPM role mapping or enforcement policy rules.

What guidelines should you follow?

Show Suggested Answer Hide Answer
Suggested Answer: D

According to the Aruba Cloud Authentication and Policy Overview1, Device Insight tags are stored in the Endpoint Repository and can be used as conditions within CPPM role mapping or enforcement policy rules. The rule condition type should be Endpoint, and the attribute should be Device Insight Tags. No extra authorization source is required for services that use policies with these rules. Therefore, option D is the correct answer.

Option A is incorrect because creating an HTTP authentication source to the Central API is not necessary to use Device Insight tags as conditions. Device Insight tags are already synchronized between Central and CPPM, and can be accessed from the Endpoint Repository.

Option B is incorrect because using the Application type for the rule conditions is not applicable to Device Insight tags. The Application type is used to match attributes from the Application Authentication source, which is used to integrate with third-party applications such as Microsoft Intune or Google G Suite.

Option C is incorrect because using the Endpoints Repository type for the rule conditions is not valid for Device Insight tags. The Endpoints Repository type is used to match attributes from the Endpoints Repository source, which is different from the Endpoint type. The Endpoints Repository source contains information about endpoints that are manually added or imported into CPPM, while the Endpoint type contains information about endpoints that are dynamically discovered and profiled by CPPM or Device Insight. Adding Endpoints Repository as a secondary authentication source for services that use policies with these rules is also unnecessary and redundant.


Contribute your Thoughts:

Charlena
5 months ago
I'm leaning towards option D, using the Endpoint type for rule conditions.
upvoted 0 times
...
Major
6 months ago
I prefer option B, using the Application type for rule conditions.
upvoted 0 times
...
Maurine
6 months ago
I think option C is also a good choice, using the Endpoints Repository type for rule conditions.
upvoted 0 times
...
Billi
6 months ago
I believe we should follow the guideline A and create an HTTP authentication source.
upvoted 0 times
...
Laura
6 months ago
I agree with Rhea, but what guidelines should we follow?
upvoted 0 times
...
Rhea
6 months ago
I think we should use Device Insight tags to improve security.
upvoted 0 times
...
Elbert
6 months ago
That's a valid point too. Each option has its own rationale to consider.
upvoted 0 times
...
Jeanice
6 months ago
I'm leaning towards option C. Using Endpoints Repository as a secondary authentication source makes sense to me.
upvoted 0 times
...
Elbert
7 months ago
I believe option A is the way to go. Creating an HTTP authentication source seems logical.
upvoted 0 times
...
Willie
7 months ago
Do you think option A is the correct approach?
upvoted 0 times
...
Jeanice
7 months ago
I agree. It's important to understand how to properly utilize these tags.
upvoted 0 times
...
Willie
7 months ago
I think we should follow the guidelines for using Device Insight tags in CPPM role mapping.
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