Question 311 of 529
Software Development SecurityeasyMultiple ChoiceObjective-mapped

Quick Answer

The answer is Static Application Security Testing (SAST) in the build stage of CI/CD. SAST is the correct choice because it analyzes source code without executing the application, allowing teams to catch vulnerabilities like injection flaws or hardcoded secrets early in the development lifecycle, right when code is compiled or built. On the CISSP exam, this question tests your understanding of secure software development and the Software Development Security domain, where you must distinguish SAST from DAST (which needs a running app) and manual reviews (too slow for continuous integration). A common trap is assuming dynamic testing fits the build stage, but remember: SAST is a white-box, shift-left approach that integrates seamlessly into automated pipelines. Memory tip: SAST = Source code Analysis, Static Testing—think “SAST scans the source, DAST scans the deployed.”

CISSP Software Development Security Practice Question

This CISSP practice question tests your understanding of software development security. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 company is implementing a CI/CD pipeline for a web application. Which security testing method should be integrated into the build stage to catch vulnerabilities early?

Question 1easymultiple choice
Full question →

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

Static Application Security Testing (SAST) in the build stage

Option B is correct because Static Application Security Testing (SAST) analyzes source code without execution, making it suitable for early detection in the build stage. Option A is wrong because DAST requires a running application. Option C is wrong because manual code review is too slow for continuous integration. Option D is wrong because relying solely on open-source tools may miss custom code flaws.

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.

  • Only using open-source vulnerability scanners

    Why it's wrong here

    Open-source scanners are useful but insufficient for custom code.

  • Dynamic Application Security Testing (DAST) in the production stage

    Why it's wrong here

    DAST should be performed later, not in the build stage.

  • Manual code review after each sprint

    Why it's wrong here

    Manual reviews are too time-intensive for continuous integration.

  • Static Application Security Testing (SAST) in the build stage

    Why this is correct

    SAST scans source code early, fitting CI/CD build stages.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Detailed technical explanation

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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 team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.

What to study next

Got this wrong? Here's your next step.

Identify which CISSP exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

Related practice questions

Related CISSP practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free CISSP practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this CISSP question test?

Software Development Security — This question tests Software Development Security — 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) in the build stage — Option B is correct because Static Application Security Testing (SAST) analyzes source code without execution, making it suitable for early detection in the build stage. Option A is wrong because DAST requires a running application. Option C is wrong because manual code review is too slow for continuous integration. Option D is wrong because relying solely on open-source tools may miss custom code flaws.

What should I do if I get this CISSP question wrong?

Identify which CISSP exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

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.