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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

PeopleCert DevSecOps Exam - Topic 6 Question 27 Discussion

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?
C) The act of validation is continuous and ongoing
A) The ad of validation is at the point of access
B) The act of validation is at the point of request
D) The act of validation focuses on credentials.

PeopleCert DevSecOps Exam - 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

by Sheridan at Mar 10, 2024, 06:22 AM

Limited Time Offer

25%

Off

Get Premium DevSecOps Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Shenika
9 months ago
B is interesting too, but I lean towards C for sure.
upvoted 0 times
...
Nettie
9 months ago
Wait, are we really saying validation is continuous? Seems a bit much.
upvoted 0 times
...
Gracia
9 months ago
I still believe in A. Point of access is where it matters most.
upvoted 0 times
...
Macy
10 months ago
Totally agree with C! It's all about ongoing checks now.
upvoted 0 times
...
Royal
10 months ago
I think C is the best choice. Validation should be continuous.
upvoted 0 times
...
Shanda
10 months ago
I vaguely recall something about validation being tied to requests in traditional models, but I’m not confident. Maybe option B?
upvoted 0 times
...
Zoila
10 months ago
I practiced a question similar to this, and I think the emphasis on ongoing validation in DevSecOps is key. So, C seems like the best choice to me.
upvoted 0 times
...
Diane
10 months ago
I’m not entirely sure, but I feel like traditional approaches focus more on credentials, which makes me lean towards option D.
upvoted 0 times
...
Celestina
11 months ago
I remember studying that in DevSecOps, validation is more about continuous monitoring rather than just at a single point. So, I think option C might be right.
upvoted 0 times
...
Nathalie
11 months ago
Hmm, this is a tough one. I'm a bit confused about the differences between the traditional and DevSecOps approaches to validation. I'll need to carefully read through the options and try to identify the key distinctions.
upvoted 0 times
...
Willard
11 months ago
I've got a good feeling about this one. The DevSecOps approach to validation seems to be more continuous and ongoing, rather than just focused on credentials at the point of access. I'll go with option C.
upvoted 0 times
...
Lou
11 months ago
Ah, this is a tricky one. I'm not entirely sure about the distinction between "at the point of access" and "at the point of request." I'll need to review my notes on DevSecOps principles to make sure I'm understanding this correctly.
upvoted 0 times
...
Barrett
11 months ago
Hmm, this question seems to be testing our understanding of the differences between traditional and DevSecOps approaches to user validation. I'll need to carefully consider the nuances of each option.
upvoted 0 times
...
Britt
11 months ago
Okay, let's see here. I think the key is to understand how the validation process differs in a DevSecOps mindset versus a more traditional approach. I'll need to really think through the implications of each answer choice.
upvoted 0 times
...
Tambra
11 months ago
Hmm, I'm a bit unsure about this one. The privacy notice is mentioned, but I'm not sure which lawful basis it would primarily refer to. I'll have to think this through step-by-step.
upvoted 0 times
...
Laquanda
11 months ago
I'm a bit confused by the wording of the question. It's asking about "two of the following statements" being correct, but there are more than two options. I'll need to read through them all and figure out which two are the right answers.
upvoted 0 times
...
Chau
11 months ago
I'm a bit stumped on this one. I know the individual methods, but I'm not sure what the combined approach would be called. I'll have to review my notes and see if I can figure this out.
upvoted 0 times
...
Rashad
11 months ago
I'm a bit confused, but I think ERC stands for requests tied to specific applications, while EIPs are broader improvements. Maybe I need to review their definitions again?
upvoted 0 times
...
Meghan
1 year 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
1 year 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
1 year 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
1 year ago
User 3: Continuous validation can be more effective in the long run.
upvoted 0 times
...
Lilli
1 year ago
User 2: I prefer just checking credentials, it's easier.
upvoted 0 times
...
Alex
1 year ago
User 1: Continuous validation is important for security.
upvoted 0 times
...
...
Donte
1 year 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
1 year 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
1 year ago
I see your point, but I still believe option C is the most effective in a DevSecOps approach.
upvoted 0 times
...
Delmy
1 year ago
Option B could also work, validation at the point of request ensures security.
upvoted 0 times
...
Diego
1 year ago
I think option A is more traditional, where validation happens at the point of access.
upvoted 0 times
...
Karan
1 year ago
Option D seems too narrow, focusing only on credentials. Continuous validation is more comprehensive.
upvoted 0 times
...
Domonique
1 year ago
I think option A is more traditional, where validation happens at the point of access.
upvoted 0 times
...
Beata
1 year ago
I agree, option C makes sense. Continuous validation is key in DevSecOps.
upvoted 0 times
...
Cammy
1 year ago
I agree, option C makes sense. Continuous validation is crucial for security.
upvoted 0 times
...
...
Lenita
1 year 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
1 year ago
I agree with Donte, continuous validation makes sense in DevSecOps.
upvoted 0 times
...
Donte
1 year ago
I think the answer is C.
upvoted 0 times
...

Save Cancel