mediumMultiple Choice
CISA Practice Question: Is developing a web application using an Agile…
An organization is developing a web application using an Agile methodology. The security team wants to integrate security testing early in the development lifecycle. Which of the following is the BEST approach to achieve this?
⚠ Common exam trap
It's easy for candidates to confuse 'early testing' with any security test performed during development, but only SAST in the CI pipeline provides automated, continuous analysis at the code level before builds are deployed.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement static application security testing (SAST) in the continuous integration pipeline
Integrating SAST into the CI pipeline allows automated scanning of source code for vulnerabilities (e.g., SQL injection, XSS) as code is committed, aligning with Agile's iterative development. This shift-left approach catches flaws early, reducing remediation cost and effort compared to later stages.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Implement static application security testing (SAST) in the continuous integration pipeline
Why this is correct
SAST scans source code without executing it, so flaws surface during coding sprints rather than after release. Embedded in the continuous integration pipeline, it gives developers immediate feedback on each commit, satisfying the Agile requirement to shift security testing early in the development lifecycle.
- ✗
Conduct a penetration test after each sprint
Why it's wrong here
While a penetration test after each sprint can identify vulnerabilities in a completed increment, it violates the Agile principle of integrating security testing *early* in the lifecycle, as the test occurs only after development is finished for that sprint. This approach is tempting because periodic penetration tests are a standard compliance requirement for production releases, and would be correct in a waterfall model where security validation gates a final deployment.
- ✗
Schedule an annual vulnerability scan of the production environment
Why it's wrong here
An annual production scan is periodic and post-deployment, so it neither integrates security early nor fits Agile's short iterations. It is tempting because vulnerability scanning is a legitimate control for live environments, but it addresses operational assurance, not early lifecycle integration.
- ✗
Perform dynamic application security testing (DAST) on deployed builds
Why it's wrong here
DAST runs against deployed builds, so findings arrive after code is written, not early in the lifecycle. It is tempting because DAST genuinely tests running applications for runtime flaws, and it would suit later assurance stages, but it cannot shift security left into Agile sprints the way static analysis or threat modelling does.
Go deeper
Related to this question
About these practice questions
This CISA question is part of Courseiva's 934-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CISA practice question is part of Courseiva's free ISACA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CISA exam.