The answer is Static Application Security Testing (SAST). SAST is the correct choice because it analyzes source code, byte code, or binary code without executing the application, making it ideal for unstable web applications where frequent code changes occur and a running environment is not yet available. By integrating SAST into the CI/CD pipeline as a pre-commit hook or automated scan, vulnerabilities like SQL injection and XSS can be caught early without hindering the iterative development process. On the CISSP exam, this question tests your understanding of when to apply SAST versus DAST—a common trap is choosing Dynamic Application Security Testing (DAST), which requires a stable, running application. Remember the key distinction: SAST is a white-box, “shift-left” approach for code in flux, while DAST is black-box for live systems. Memory tip: “SAST scans the source, DAST tests the course.”
CISSP Security Assessment and Testing Practice Question
This CISSP practice question tests your understanding of security assessment and testing. Compare every option against the stated constraints before choosing — the best answer satisfies all requirements, not just the most obvious one. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A security analyst is tasked with identifying vulnerabilities in a web application that is still in development. The application code is not yet stable, and frequent changes are expected. Which testing approach would be most appropriate to identify vulnerabilities without hindering the development process?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Static application security testing (SAST)
Static Application Security Testing (SAST) is the most appropriate approach because it analyzes source code, byte code, or binary code without executing the application, making it ideal for early-stage development where code is unstable and frequently changing. SAST can be integrated into the development pipeline (e.g., as a pre-commit hook or CI/CD step) to identify vulnerabilities like SQL injection, XSS, or buffer overflows without requiring a running application or hindering the iterative development process.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Fuzz testing
Why it's wrong here
Used for finding input handling bugs, not comprehensive vulnerability identification.
✗
Manual penetration testing
Why it's wrong here
Too resource-intensive and not suitable for frequent changes.
✓
Static application security testing (SAST)
Why this is correct
Can be integrated into CI/CD and analyze source code without a runtime environment.
Related concept
Read the scenario before looking for a memorised answer.
✗
Dynamic application security testing (DAST)
Why it's wrong here
Requires a running application and may miss vulnerabilities in early development.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose DAST (Option D) because they associate 'dynamic' with 'real-world testing,' but they overlook the critical constraint that the application is unstable and in development, making SAST the only viable option that does not require a running application.
Detailed technical explanation
How to think about this question
SAST tools, such as Checkmarx or Fortify, perform data flow analysis, control flow analysis, and taint tracking to trace untrusted input from entry points (e.g., HTTP request parameters) to sensitive sinks (e.g., SQL queries), flagging potential vulnerabilities without executing the code. A subtle behavior is that SAST can produce false positives due to incomplete path analysis or lack of runtime context (e.g., sanitization functions that are not recognized), requiring developers to triage results. In a real-world CI/CD pipeline, SAST is often run on every commit to catch issues early, whereas DAST is reserved for later stages when a staging environment is stable.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security analyst at a medium-sized enterprise encounters this scenario during an investigation or architecture review. The correct answer reflects best practice for the specific threat or control described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Security exam questions test whether you can match controls to threats in context — not just recall definitions.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CISSP question in full detail.
Security Assessment and Testing — This question tests Security Assessment and Testing — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Static application security testing (SAST) — Static Application Security Testing (SAST) is the most appropriate approach because it analyzes source code, byte code, or binary code without executing the application, making it ideal for early-stage development where code is unstable and frequently changing. SAST can be integrated into the development pipeline (e.g., as a pre-commit hook or CI/CD step) to identify vulnerabilities like SQL injection, XSS, or buffer overflows without requiring a running application or hindering the iterative development process.
What should I do if I get this CISSP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CISSP practice question is part of Courseiva's free ISC2 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 CISSP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.