D. Before launch after all code for a feature is complete.
Explanation:
Code audits should be concluded after all code for a feature is complete but before it is launched. This allows for a thorough review of the entire codebase related to the feature, ensuring that all potential security vulnerabilities and compliance issues are identified and addressed before the code is deployed to production. This timing helps in catching any issues that might have been missed during earlier stages and ensures that the final product meets all security and quality standards.
The correct answer id D.
When to Conduct Code Audits:
Before Launch: Audits should be concluded before launching a feature or releasing the software.
Throughout Development: Regular audits during development catch issues early.
Code audits are also known as SAST and should be done after a feature is completed, so the code can be reviewed and then you run a DAST (dynamic auditing on the compiled code) before completing the development
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Ssourav
3 months agoofirga
9 months, 1 week agoME79
2 years, 1 month ago187san
2 years, 11 months ago837vq3
3 years agok4d4v4r
3 years agoam2005
2 years, 7 months ago