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

Splunk Exam SPLK-3001 Topic 1 Question 80 Discussion

Actual exam question for Splunk's SPLK-3001 exam
Question #: 80
Topic #: 1
[All SPLK-3001 Questions]

Following the Installation of ES, an admin configured Leers with the ss_uso r role the ability to close notable events. How would the admin restrict these users from being able to change the status of Resolved notable events to closed?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Jean
10 days ago
C) is a bold move, giving the ess_user role the own Notable Events permission. I hope they have a good reason for that!
upvoted 0 times
...
Marsha
18 days ago
D) is an interesting option, but it would remove the ess_user role's ability to edit any notable events, not just the Resolved ones.
upvoted 0 times
...
Glenn
21 days ago
I'm not sure, but I think option D could also work. Removing the edit_notable_events capability from the ess_user role would limit their ability to close notable events.
upvoted 0 times
...
Lauran
22 days ago
B) is not the right answer, as it would remove the ess_user role from the status transitions for the Resolved status, not the Closed status.
upvoted 0 times
...
Salome
23 days ago
I agree with Ceola. That makes sense. It's important to restrict access to prevent unauthorized changes.
upvoted 0 times
...
Aileen
27 days ago
A) seems like the correct answer, as it restricts the ess_user role from being able to change the status of Resolved notable events to closed.
upvoted 0 times
Ulysses
2 days ago
A) seems like the correct answer, as it restricts the ess_user role from being able to change the status of Resolved notable events to closed.
upvoted 0 times
...
...
Ceola
1 months ago
I think the answer is A. By removing ess_user from the status transitions for the closed status, they won't be able to change the status of Resolved notable events to closed.
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