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

PeopleCert Exam DevSecOps Topic 6 Question 27 Discussion

Actual exam question for PeopleCert's DevSecOps exam
Question #: 27
Topic #: 6
[All DevSecOps Questions]

When of the following BEST describes now the security principle of validation of a user's access and actions differ within a DevSecOps mindset versus a more traditional approach to this principle?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Meghan
2 months ago
Wait, we're supposed to validate users' actions too? I thought we just needed to check their credentials. This DevSecOps thing sounds like a lot of extra work.
upvoted 0 times
...
Irma
2 months ago
I agree with Gayla. Continuous validation is key in a DevSecOps environment. You can't just rely on credentials and hope for the best. Security has to be baked in at every step.
upvoted 0 times
...
Lettie
2 months ago
Ha! Continuous validation? Sounds like a lot of work. I'll just stick with the good old-fashioned credentials check. Easy peasy!
upvoted 0 times
Rosio
22 days ago
User 3: Continuous validation can be more effective in the long run.
upvoted 0 times
...
Lilli
23 days ago
User 2: I prefer just checking credentials, it's easier.
upvoted 0 times
...
Alex
25 days ago
User 1: Continuous validation is important for security.
upvoted 0 times
...
...
Donte
2 months ago
I'm not sure about that. Shouldn't the validation be at the point of request rather than just at the point of access? That seems more secure to me.
upvoted 0 times
...
Gayla
2 months ago
I think option C is the best answer. In a DevSecOps mindset, the validation of user access and actions is a continuous process, not just a one-time check at the point of access or request.
upvoted 0 times
Lamar
20 days ago
I see your point, but I still believe option C is the most effective in a DevSecOps approach.
upvoted 0 times
...
Delmy
25 days ago
Option B could also work, validation at the point of request ensures security.
upvoted 0 times
...
Diego
29 days ago
I think option A is more traditional, where validation happens at the point of access.
upvoted 0 times
...
Karan
1 months ago
Option D seems too narrow, focusing only on credentials. Continuous validation is more comprehensive.
upvoted 0 times
...
Domonique
2 months ago
I think option A is more traditional, where validation happens at the point of access.
upvoted 0 times
...
Beata
2 months ago
I agree, option C makes sense. Continuous validation is key in DevSecOps.
upvoted 0 times
...
Cammy
2 months ago
I agree, option C makes sense. Continuous validation is crucial for security.
upvoted 0 times
...
...
Lenita
3 months ago
I'm not sure, but I think D could also be a valid option since credentials are important for validation.
upvoted 0 times
...
Margarita
4 months ago
I agree with Donte, continuous validation makes sense in DevSecOps.
upvoted 0 times
...
Donte
4 months ago
I think the answer is C.
upvoted 0 times
...

Save Cancel