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

Salesforce Exam Development Lifecycle and Deployment Architect Topic 4 Question 25 Discussion

Actual exam question for Salesforce's Development Lifecycle and Deployment Architect exam
Question #: 25
Topic #: 4
[All Development Lifecycle and Deployment Architect Questions]

Universal Containers CUC) has decided to improve the quality of work by the development teams. As part of the effort, UC has acquired some code review software licenses to help the developers with code quality.

Which are two recommended practices to follow when conducting secure code reviews? Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Lacresha
25 days ago
A and C are the way to go, no doubt. Can't have those developers slacking off, am I right? Although, I do hope the code review software has a 'shame the developer' feature. That would be hilarious!
upvoted 0 times
...
Oren
26 days ago
Combining human effort and automatic checks is the way to go. Gotta catch those sneaky bugs! Although, I do have to wonder if the code review software will give me a gold star for every flaw I find. *wink wink*
upvoted 0 times
...
Crista
27 days ago
Focusing on aggregated reviews? I don't think that's a good idea. You need to review each meaningful change to ensure quality. And using the tool to call out individual developers? That's just asking for trouble!
upvoted 0 times
Pauline
10 days ago
A) Generate a code review checklist to ensure consistency between reviews and different reviewers.
upvoted 0 times
...
...
Nickie
1 months ago
Generating a code review checklist is definitely a must to ensure consistency. Automatic checks are also key to catch any potential flaws that human eyes might miss.
upvoted 0 times
Sophia
8 days ago
C) Conduct a review that combines human efforts and automatic checks by the tool to detect all flaws.
upvoted 0 times
...
Lilli
1 months ago
A) Generate a code review checklist to ensure consistency between reviews and different reviewers.
upvoted 0 times
...
...
Dick
2 months ago
I'm not sure about B and D. Focusing on aggregated reviews may miss important details, and blaming developers for errors may not be productive.
upvoted 0 times
...
Benedict
2 months ago
I agree with Colette. A checklist for consistency and combining human efforts with automatic checks sound like good practices.
upvoted 0 times
...
Colette
2 months ago
I think A and C are the recommended practices for secure code reviews.
upvoted 0 times
...

Save Cancel