CAS-003 · Question #639
A software development firm wants to validate the use of standard libraries as part of the software development process. Each developer performs unit testing prior to committing changes to the code…
The correct answer is A. Static analysis. Static analysis (SAST) examines source code without executing it, making it ideal for automated integration into a CI/CD pipeline immediately after a commit and before branching. It catches vulnerabilities, insecure coding patterns, and deviations from coding standards early…
Question
A software development firm wants to validate the use of standard libraries as part of the software development process. Each developer performs unit testing prior to committing changes to the code repository. Which of the following activities would be BEST to perform after a commit but before the creation of a branch?
Options
- AStatic analysis
- BHeuristic analysis
- CDynamic analysis
- DWeb application vulnerability scanning
- EPenetration testing
How the community answered
(63 responses)- A87% (55)
- B6% (4)
- C2% (1)
- D2% (1)
- E3% (2)
Explanation
Static analysis (SAST) examines source code without executing it, making it ideal for automated integration into a CI/CD pipeline immediately after a commit and before branching. It catches vulnerabilities, insecure coding patterns, and deviations from coding standards early and at scale. Answer B (heuristic analysis) is primarily a malware-detection technique used by antivirus tools, not a code validation method. Answer C (dynamic analysis) requires the application to be running and is better suited later in the pipeline. Answer D (web application vulnerability scanning) and Answer E (penetration testing) are later-stage activities performed against deployed or near-deployed applications-not appropriate at the pre-branch code commit stage.
Topics
Community Discussion
No community discussion yet for this question.