The correct answer is to replace the concatenated query with a prepared statement and bind parameters, as this is the most effective remediation for SQL injection in Java web applications. This approach works because prepared statements, or parameterized queries, strictly separate SQL logic from user-supplied data; by using bind variables like `ps.setString(1, user)`, the database engine treats the input as data only, never as executable code, thereby neutralizing injection attempts entirely. On the CISSP exam, this concept tests your understanding of secure coding practices within the Software Development Security domain, often appearing as a trap where developers mistakenly rely on input validation or escaping instead of parameterization. A common memory tip is to remember that prepared statements “prepare the plan first, then plug in the data”—if the SQL structure is fixed before any user input touches it, injection is impossible.
CISSP Software Development Security Practice Question
This CISSP practice question tests your understanding of software development security. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
During a code review, a developer encounters the following code snippet in a Java web application used to authenticate users:
String query = "SELECT * FROM users WHERE username = '" + request.getParameter("user") + "' AND password = '" + request.getParameter("pass") + "'";
Which of the following is the MOST effective remediation?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Replace the concatenated query with a prepared statement and bind parameters
Option D is correct because prepared statements with parameterized queries separate SQL logic from user input, preventing SQL injection entirely. In Java, using PreparedStatement with bind variables (e.g., `ps.setString(1, user)`) ensures the database treats input as data, not executable code, which is the only reliable defense against SQL injection attacks.
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.
✗
Use regular expressions to validate the username and password inputs
Why it's wrong here
Input validation alone is not sufficient; SQL injection can still occur through encoding bypasses.
✗
Encode the input using HTML entity encoding before inclusion in the query
Why it's wrong here
HTML encoding is for XSS, not SQL injection; it does not prevent SQL injection.
✗
Escape single quotes in the input parameters
Why it's wrong here
Escaping is error-prone and may be bypassed; prepared statements are the recommended defense.
✓
Replace the concatenated query with a prepared statement and bind parameters
Why this is correct
Prepared statements ensure user input is treated as data, not executable SQL.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose input validation (Option A) or escaping (Option C) because they seem like reasonable security measures, but the CISSP exam emphasizes that parameterized queries/prepared statements are the definitive, defense-in-depth solution for SQL injection, not ad-hoc sanitization.
Detailed technical explanation
How to think about this question
Under the hood, a prepared statement precompiles the SQL query with placeholders (e.g., `?`), and the database engine compiles the query plan before any user data is bound. This ensures that even if an attacker inputs `' OR '1'='1`, it is treated as a literal string value, not as SQL syntax. In Java, using `PreparedStatement` with `setString()` also handles character encoding and escaping automatically, avoiding common pitfalls like Unicode normalization or driver-specific escape sequences.
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 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.
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: Replace the concatenated query with a prepared statement and bind parameters — Option D is correct because prepared statements with parameterized queries separate SQL logic from user input, preventing SQL injection entirely. In Java, using PreparedStatement with bind variables (e.g., `ps.setString(1, user)`) ensures the database treats input as data, not executable code, which is the only reliable defense against SQL injection attacks.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Refer to the exhibit. Which vulnerability does this code contain?
easy
✓ A.SQL injection
B.Command injection
C.Buffer overflow
D.Cross-site scripting (XSS)
Why A: Option A is correct because the code concatenates user input directly into an SQL query, allowing SQL injection. Option B is wrong because buffer overflow is not present. Option C is wrong because XSS occurs in web output. Option D is wrong because command injection involves system commands, not SQL.
Variation 2. During a code review, a developer identifies a SQL injection vulnerability. What is the most effective fix?
easy
A.Use stored procedures exclusively.
B.Use an ORM framework.
C.Escape all input.
✓ D.Implement parameterized queries.
Why D: Parameterized queries (prepared statements) ensure user input is treated as data, not executable code. Stored procedures can still be vulnerable if dynamically built. Escaping input is error-prone. ORMs often use SQL underneath and may not prevent injection if misused.
Variation 3. Which TWO of the following are mandatory secure coding practices to prevent injection attacks? (Select exactly two.)
medium
A.Encode output to the browser
B.Encrypt sensitive input data
C.Use custom error messages that detail the failure
✓ D.Use parameterized queries or prepared statements
✓ E.Validate and sanitize all user input
Why D: Options A and D are correct. Input validation ensures data conforms to expected patterns; parameterized queries separate code from data. Option B is wrong because encoding outputs is for XSS, not injection. Option C is wrong because error messages should not reveal internal details. Option E is wrong because encryption does not prevent injection.
Last reviewed: Jun 11, 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.
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.