The answer is enabling safe checks or anti-false positive mode. This configuration reduces false positives by instructing the scanner to send payloads that respect the application’s expected input constraints, such as field length limits or character restrictions, rather than oversized or malformed payloads that get truncated or rejected. When a scanner blindly sends oversized payloads, the application’s normal truncation logic is misinterpreted as a vulnerability, but safe checks ensure the scanner only flags flaws that are truly exploitable under realistic conditions. On the CompTIA PenTest+ PT0-002 exam, this concept tests your ability to tune scanner behavior to match real-world application behavior, a common trap being that testers mistakenly adjust scan intensity or port ranges instead. A useful memory tip: think “safe checks = size checks” — the scanner checks payload size against expected limits before reporting a finding.
PT0-002 Practice Question: Information Gathering and Vulnerability Scanning
This PT0-002 practice question tests your understanding of information gathering and vulnerability scanning. 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.
A penetration tester is using a vulnerability scanner on a web application and notices that many findings are false positives caused by the scanner sending oversized payloads that the application truncates or rejects. Which scanner configuration change would MOST effectively reduce false positives in this scenario?
Why wrong: Higher intensity typically increases the number of requests and can lead to more false positives, not fewer.
B
Enable safe checks or anti-false positive mode
Safe checks use additional verification steps to confirm a vulnerability before reporting it, reducing false positives.
C
Increase the HTTP request timeout
Why wrong: Timeout adjustments handle slow responses, not the accuracy of vulnerability detection.
D
Disable vulnerability detection for certain plugins
Why wrong: Disabling checks reduces false positives but also risks missing real vulnerabilities; it is not a targeted solution for payload truncation issues.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable safe checks or anti-false positive mode
Enabling safe checks or anti-false positive mode configures the scanner to send payloads that conform to expected application input constraints (e.g., length limits, character sets) rather than oversized or malformed payloads. This reduces false positives by ensuring that the scanner only reports vulnerabilities that are actually reachable and exploitable under normal application behavior, rather than triggering truncation or rejection logic that is not a security flaw.
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 send more payloads
Why it's wrong here
Higher intensity typically increases the number of requests and can lead to more false positives, not fewer.
✓
Enable safe checks or anti-false positive mode
Why this is correct
Safe checks use additional verification steps to confirm a vulnerability before reporting it, reducing false positives.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the HTTP request timeout
Why it's wrong here
Timeout adjustments handle slow responses, not the accuracy of vulnerability detection.
✗
Disable vulnerability detection for certain plugins
Why it's wrong here
Disabling checks reduces false positives but also risks missing real vulnerabilities; it is not a targeted solution for payload truncation issues.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse 'increasing scan intensity' with 'more thorough testing,' but in reality, it amplifies the very behavior (oversized payloads) that causes false positives, while 'safe checks' directly mitigates the root cause.
Detailed technical explanation
How to think about this question
Many vulnerability scanners, such as Nessus or OpenVAS, include a 'safe checks' mode that disables intrusive or potentially disruptive tests and instead relies on banner grabbing, version detection, and non-intrusive probes. In the context of web application scanning, this mode often limits payload sizes to within RFC 2616 (HTTP/1.1) or application-defined limits, preventing the scanner from sending payloads that exceed the application's input buffer, which would otherwise be truncated and falsely flagged as a vulnerability (e.g., buffer overflow).
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: Enable safe checks or anti-false positive mode — Enabling safe checks or anti-false positive mode configures the scanner to send payloads that conform to expected application input constraints (e.g., length limits, character sets) rather than oversized or malformed payloads. This reduces false positives by ensuring that the scanner only reports vulnerabilities that are actually reachable and exploitable under normal application behavior, rather than triggering truncation or rejection logic that is not a security flaw.
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.