The answer is to correlate the scanner output with manual verification and document the discrepancy. This is correct because handling false positives in vulnerability scanning requires a two-step validation process: automated tools flag potential issues based on signatures, but only manual testing can confirm whether input sanitization or other controls actually mitigate the risk. On the CompTIA PenTest+ PT0-002 exam, this scenario tests your understanding of the information gathering and vulnerability scanning phase, where the common trap is to blindly trust automated results or to ignore the finding entirely. Instead, you must document the false positive to refine future scans and avoid wasted effort. A useful memory tip is “Verify, then archive”—always manually confirm a scanner’s alert before dismissing it, and keep a record of the discrepancy to sharpen your scanning methodology.
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 vulnerability scan of a web application, the penetration tester notices that the scanner reports a critical SQL injection vulnerability in the login parameter. However, manual testing confirms that the input is properly sanitized and the vulnerability is a false positive. Which of the following actions should the tester take to ensure accurate vulnerability identification and avoid wasting time on false positives in future scans?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Correlate the scanner output with manual verification and document the discrepancy
Option B is correct because the penetration tester should correlate automated scanner output with manual verification to confirm findings, then document the discrepancy for future reference. This ensures accurate vulnerability identification by leveraging human analysis to filter false positives, which is a standard practice in PT0-002 methodology for information gathering and vulnerability scanning.
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.
✗
Increase the scan intensity to ensure the vulnerability is accurately detected
Why it's wrong here
Increasing intensity does not fix false positives; it may create more noise.
✓
Correlate the scanner output with manual verification and document the discrepancy
Why this is correct
This ensures accurate reporting and improves future scan tuning.
Related concept
Read the scenario before looking for a memorised answer.
✗
Modify the scanner's configuration to exclude false positive patterns
Why it's wrong here
This could exclude legitimate vulnerabilities and is not recommended without analysis.
✗
Ignore the finding and proceed with manual testing only
Why it's wrong here
Ignoring automated findings may miss real vulnerabilities.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think modifying scanner configuration (Option C) is the immediate fix, but PT0-002 emphasizes documenting and correlating findings before making changes to avoid masking real vulnerabilities.
Detailed technical explanation
How to think about this question
False positives in SQL injection scans often arise from heuristic-based detection that flags parameterized queries as vulnerable if the scanner's payloads cause benign database errors (e.g., MySQL error 1064) without actual injection. In real-world scenarios, a tester might encounter this when a web application uses prepared statements with bound parameters, which are immune to SQL injection but can still trigger scanner alerts due to incomplete response analysis. Documenting such discrepancies helps refine scanner rules or create custom exceptions in tools like Nessus or Burp Suite, ensuring future scans focus on genuine risks.
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 PT0-002 question in full detail.
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: Correlate the scanner output with manual verification and document the discrepancy — Option B is correct because the penetration tester should correlate automated scanner output with manual verification to confirm findings, then document the discrepancy for future reference. This ensures accurate vulnerability identification by leveraging human analysis to filter false positives, which is a standard practice in PT0-002 methodology for information gathering and vulnerability scanning.
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.
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 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.