- A
The scanner used a payload that caused a different error unrelated to SQL injection
Why wrong: While possible, the most common reason is that the scanner incorrectly interpreted a non-SQL error as evidence of injection.
- B
The scanner detected a stored XSS instead
Why wrong: Stored XSS and SQL injection are different vulnerability types; the scanner would not confuse them if properly configured.
- C
The scanner matched a generic error message that is not specific to SQL injection
Scanners often use keyword matching and will flag any page that returns a database error string, even if the vulnerability does not exist.
- D
The scanner tested a different parameter than what was reported
Why wrong: This is unlikely; the scanner typically reports the exact parameter it tested.
Quick Answer
The answer is that the scanner matched a generic error message that is not specific to SQL injection. This occurs because vulnerability scanners often rely on pattern matching in HTTP responses, flagging any generic error message—like "An error occurred"—as evidence of SQL injection, even when the application uses parameterized queries that safely handle malicious input. On the CompTIA PenTest+ PT0-002 exam, this question tests your ability to distinguish between automated scan results and manual validation, a critical skill for avoiding false positives during penetration tests. A common trap is assuming any error response after a SQL payload indicates a real vulnerability, but the key is to verify whether the error message is database-specific (e.g., "MySQL syntax error") or a generic application error. Memory tip: If the error message could appear for any broken input, it’s a false positive—think "generic equals generic."
PT0-002 Practice Question: Information Gathering and Vulnerability Scanning
This PT0-002 practice question tests your understanding of information gathering and vulnerability scanning. 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.
During a penetration test, a vulnerability scanner reports a critical SQL injection vulnerability in a web application. However, manual testing shows that the parameter is not injectable due to proper parameterized queries. Which of the following is the MOST likely cause of this false positive?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
The scanner matched a generic error message that is not specific to SQL injection
A vulnerability scanner often relies on pattern matching in HTTP responses to flag SQL injection. If the application returns a generic error message (e.g., 'An error occurred') after sending a malicious payload, the scanner may incorrectly classify it as SQL injection. However, because the application uses parameterized queries, the payload is safely handled, and the error is unrelated to SQL syntax — making this a classic false positive caused by generic error message matching.
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.
- ✗
The scanner used a payload that caused a different error unrelated to SQL injection
Why it's wrong here
While possible, the most common reason is that the scanner incorrectly interpreted a non-SQL error as evidence of injection.
- ✗
The scanner detected a stored XSS instead
Why it's wrong here
Stored XSS and SQL injection are different vulnerability types; the scanner would not confuse them if properly configured.
- ✓
The scanner matched a generic error message that is not specific to SQL injection
Why this is correct
Scanners often use keyword matching and will flag any page that returns a database error string, even if the vulnerability does not exist.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The scanner tested a different parameter than what was reported
Why it's wrong here
This is unlikely; the scanner typically reports the exact parameter it tested.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume a scanner's SQL injection flag must be caused by an actual SQL error, when in fact scanners often rely on generic error message patterns that can be triggered by any application exception.
Trap categories for this question
Similar concept trap
Stored XSS and SQL injection are different vulnerability types; the scanner would not confuse them if properly configured.
Detailed technical explanation
How to think about this question
Vulnerability scanners like Nessus or OpenVAS often use simple regex patterns (e.g., matching 'SQL syntax' or 'mysql_fetch') in the response body to infer SQL injection. When parameterized queries are used, the database driver treats user input as data, not executable code, so even malformed input results in a safe query execution. A real-world scenario involves legacy applications that return a generic 500 error page for any exception, causing scanners to falsely report SQLi when the actual issue is a type conversion error or a missing resource.
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.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Information Gathering and Vulnerability Scanning — study guide chapter
Learn the concepts, then practise the questions
- →
Information Gathering and Vulnerability Scanning practice questions
Targeted practice on this topic area only
- →
All PT0-002 questions
509 questions across all exam domains
- →
CompTIA PenTest+ PT0-002 study guide
Full concept coverage aligned to exam objectives
- →
PT0-002 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PT0-002 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Planning and Scoping practice questions
Practise PT0-002 questions linked to Planning and Scoping.
Information Gathering and Vulnerability Scanning practice questions
Practise PT0-002 questions linked to Information Gathering and Vulnerability Scanning.
Attacks and Exploits practice questions
Practise PT0-002 questions linked to Attacks and Exploits.
Reporting and Communication practice questions
Practise PT0-002 questions linked to Reporting and Communication.
Tools and Code Analysis practice questions
Practise PT0-002 questions linked to Tools and Code Analysis.
PT0-002 fundamentals practice questions
Practise PT0-002 questions linked to PT0-002 fundamentals.
PT0-002 scenario practice questions
Practise PT0-002 questions linked to PT0-002 scenario.
PT0-002 troubleshooting practice questions
Practise PT0-002 questions linked to PT0-002 troubleshooting.
Practice this exam
Start a free PT0-002 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 PT0-002 question test?
Information Gathering and Vulnerability Scanning — This question tests Information Gathering and Vulnerability Scanning — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The scanner matched a generic error message that is not specific to SQL injection — A vulnerability scanner often relies on pattern matching in HTTP responses to flag SQL injection. If the application returns a generic error message (e.g., 'An error occurred') after sending a malicious payload, the scanner may incorrectly classify it as SQL injection. However, because the application uses parameterized queries, the payload is safely handled, and the error is unrelated to SQL syntax — making this a classic false positive caused by generic error message matching.
What should I do if I get this PT0-002 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
Last reviewed: Jun 11, 2026
This PT0-002 practice question is part of Courseiva's free CompTIA 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 PT0-002 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.