The answer is requiring all pull requests to be approved by at least one peer reviewer, as this practice best ensures that code changes are reviewed for security issues before merging into the main branch. Mandatory peer review embeds human judgment into the development pipeline, allowing reviewers to catch logic flaws, injection vulnerabilities, and insecure design patterns that automated tools often miss. On the CISSP exam, this question tests your understanding of the Software Development Security domain, specifically how secure code review practices integrate with version control workflows. A common trap is choosing static analysis or unit tests alone, but remember that automated scanning complements—not replaces—human review. For a memory tip, think “PR before merge, human eyes catch the surge”—peer review is the gatekeeper for security, not just functionality.
CISSP Software Development Security Practice Question
This CISSP practice question tests your understanding of software development security. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
An organization uses a version control system for all software development. Which practice best ensures that code changes are reviewed for security issues before merging into the main branch?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Requiring all pull requests to be approved by at least one peer reviewer.
Option A is correct because mandatory peer review (pull request review) allows reviewers to examine code for security flaws before integration. Option B is wrong because static analysis alone may miss logic flaws, and automated scanning should complement human review. Option C is wrong because automated unit tests typically do not test security. Option D is wrong because pre-commit hooks are limited to client-side checks, not a robust review 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.
✓
Requiring all pull requests to be approved by at least one peer reviewer.
Why this is correct
Peer review is a manual review process that can catch security issues that automated tools miss.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Configuring the CI pipeline to run static analysis tools only on the main branch.
Why it's wrong here
Running analysis only on main branch misses issues introduced in feature branches.
✗
Enforcing that all commits pass automated unit tests before merging.
Why it's wrong here
Unit tests often do not cover security vulnerabilities.
✗
Using pre-commit hooks to scan for secrets in code before commit.
Why it's wrong here
Pre-commit hooks help prevent secrets from being committed but are not a substitute for code review.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CISSP question in full detail.
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.
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: Requiring all pull requests to be approved by at least one peer reviewer. — Option A is correct because mandatory peer review (pull request review) allows reviewers to examine code for security flaws before integration. Option B is wrong because static analysis alone may miss logic flaws, and automated scanning should complement human review. Option C is wrong because automated unit tests typically do not test security. Option D is wrong because pre-commit hooks are limited to client-side checks, not a robust review process.
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.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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.