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?
I'm a bit confused about the difference between the own Notable Events permission and the status transitions. Could option C actually help in this scenario?
I remember a similar question where we had to manage user roles and permissions. I feel like option A makes the most sense since we want to prevent changes to Resolved events.
This is a good question to test our understanding of Splunk Enterprise Security permissions. I'd recommend carefully reviewing the status configuration and access control settings to ensure we're addressing the specific requirement here.
Hmm, I'm a bit confused here. The question is asking about restricting users from changing the status of Resolved notable events, but the answer options seem to be talking about the Closed status. I'll need to re-read this carefully to make sure I understand the exact problem.
This looks like a straightforward question about restricting user permissions in Splunk Enterprise Security. I think the key is to focus on the status transitions and remove the ess_user role from being able to change the status to Closed.
Okay, I think I've got it now. The admin needs to remove the ess_user role from the status transitions for the Closed status, so that they can't change Resolved notable events to Closed. Option A looks like the right answer to me.
This is a tricky one. I'm not sure if VLAN, VRF, or VXLAN is the best fit. I'll need to re-read the question carefully and think through the pros and cons of each option.
Okay, let me think this through. The question is asking about the advantages of self-healing tech, so I need to focus on which option best describes that. I'm leaning towards Option D, as reducing the cost of support seems like a key benefit of this kind of technology.
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.
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
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Yuriko
3 months agoMila
3 months agoIola
4 months agoArmanda
4 months agoVenita
4 months agoPedro
4 months agoJeff
4 months agoJonell
4 months agoAnthony
5 months agoEmily
5 months agoNobuko
5 months agoTijuana
5 months agoMee
5 months agoRebbeca
5 months agoColene
5 months agoHuey
10 months agoArthur
8 months agoRegenia
8 months agoElliot
8 months agoJean
10 months agoLawrence
8 months agoVirgie
9 months agoAlyce
9 months agoVal
9 months agoWinfred
9 months agoIrma
9 months agoValentine
10 months agoMarsha
10 months agoJustine
9 months agoCorazon
9 months agoJettie
9 months agoHaydee
10 months agoGlenn
10 months agoLauran
10 months agoSalome
11 months agoAileen
11 months agoGilma
9 months agoChauncey
9 months agoCherry
9 months agoUlysses
10 months agoCeola
11 months ago