Quick Answer
The answer is a vulnerability scan with a low-thread count. This is correct because reducing the number of concurrent threads directly limits the volume of packets and connections sent to the target, thereby minimizing CPU, memory, and network overhead on the production server. On the CompTIA PenTest+ PT0-002 exam, this scenario tests your understanding of how to balance thoroughness with operational safety—a common trap is choosing a stealth scan, which focuses on evasion rather than performance impact. The key distinction is that low-thread scanning throttles intensity to avoid service disruption while still performing a legitimate assessment. Remember the memory tip: “Low threads, low load” to keep production servers from going down.
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.
A tester is performing a vulnerability scan against a critical production server. The client requests minimal impact on system performance. Which scan type should the tester use?
TCP connect scan
Why wrong: TCP connect scans are complete connections and can be heavy.
Vulnerability scan with low-thread count
Low thread count minimizes system impact while still performing the scan.
Aggressive Nmap scan
Why wrong: Aggressive scans generate high traffic and may impact performance.
Stealth SYN scan
Why wrong: Stealth scans still send many packets and may cause load.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Vulnerability scan with low-thread count
Option B is correct because a vulnerability scan with a low-thread count reduces the number of concurrent connections and packets sent to the target, minimizing CPU, memory, and network overhead on the production server. This directly addresses the client's requirement for minimal performance impact while still performing a legitimate security assessment. Unlike aggressive or stealth scans, this approach throttles the scan intensity to avoid service disruption.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
TCP connect scan
Why it's wrong here
TCP connect scans are complete connections and can be heavy.
Vulnerability scan with low-thread count
Why this is correct
Low thread count minimizes system impact while still performing the scan.
Related concept
Read the scenario before looking for a memorised answer.
Aggressive Nmap scan
Why it's wrong here
Aggressive scans generate high traffic and may impact performance.
Stealth SYN scan
Why it's wrong here
Stealth scans still send many packets and may cause load.
Common exam traps
The trap here is that candidates often assume 'stealth' (SYN scan) is always the safest choice for production systems, but the question specifically asks for minimal performance impact, which is controlled by scan intensity (thread count) rather than scan type alone.
Detailed technical explanation
Vulnerability scanners like Nessus, OpenVAS, or Qualys allow configuration of 'max concurrent checks' or 'thread count' to control resource usage. A low-thread count (e.g., 5–10 threads) ensures the scanner sends probes slowly, reducing the likelihood of triggering rate limits, connection timeouts, or CPU spikes on the target. In contrast, Nmap's -T4 or -T5 settings can send hundreds of packets per second, which is suitable for lab environments but risky for production systems.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PT0-002 questions linked to Planning and Scoping.
Practise PT0-002 questions linked to Information Gathering and Vulnerability Scanning.
Practise PT0-002 questions linked to Attacks and Exploits.
Practise PT0-002 questions linked to Reporting and Communication.
Practise PT0-002 questions linked to Tools and Code Analysis.
Practise PT0-002 questions linked to PT0-002 fundamentals.
Practise PT0-002 questions linked to PT0-002 scenario.
Practise PT0-002 questions linked to PT0-002 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Information Gathering and Vulnerability Scanning — This question tests Information Gathering and Vulnerability Scanning — Read the scenario before looking for a memorised answer..
The correct answer is: Vulnerability scan with low-thread count — Option B is correct because a vulnerability scan with a low-thread count reduces the number of concurrent connections and packets sent to the target, minimizing CPU, memory, and network overhead on the production server. This directly addresses the client's requirement for minimal performance impact while still performing a legitimate security assessment. Unlike aggressive or stealth scans, this approach throttles the scan intensity to avoid service disruption.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 25, 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.