- A
Report the finding with contextual risk adjustment and explain that the vulnerable service is disabled and not reachable.
This preserves evidence while avoiding overstating exploitability.
- B
Delete the finding because the package exists but is not currently exploitable.
Why wrong: The condition is still relevant and should be documented.
- C
Report it as critical without context because the scanner assigned critical severity.
Why wrong: Scanner severity must be validated and contextualized.
- D
Exploit the service by enabling it first.
Why wrong: Changing service state to create exploitability is not appropriate unless explicitly authorized.
Quick Answer
The correct answer is to report the finding with contextual risk adjustment and explain that the vulnerable service is disabled and not reachable. This is because penetration testing requires moving beyond raw scanner output to manual verification; while the vulnerable package exists, the disabled service eliminates the attack vector, so the risk must be adjusted downward to reflect the true exploitability. On the CompTIA PenTest+ PT0-002 exam, this tests your understanding of risk scoring and the importance of validating findings, a common trap being to simply report the critical severity as-is without context. A key memory tip is "package present, service absent" — always adjust risk based on reachability, not just presence.
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.
A vulnerability scanner reports an unauthenticated critical finding on an internal server. Manual testing shows the vulnerable package is present, but the vulnerable service is disabled and not reachable. How should the tester report this?
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
Report the finding with contextual risk adjustment and explain that the vulnerable service is disabled and not reachable.
Option A is correct because the vulnerability scanner identified a real package vulnerability, but manual verification revealed the service is disabled and unreachable. The tester must report the finding with a contextual risk adjustment to accurately reflect the reduced exploitability, as per standard risk assessment practices in penetration testing. This ensures the organization understands the actual risk without ignoring the presence of the vulnerable package, which could be enabled in the future.
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.
- ✓
Report the finding with contextual risk adjustment and explain that the vulnerable service is disabled and not reachable.
Why this is correct
This preserves evidence while avoiding overstating exploitability.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Delete the finding because the package exists but is not currently exploitable.
Why it's wrong here
The condition is still relevant and should be documented.
- ✗
Report it as critical without context because the scanner assigned critical severity.
Why it's wrong here
Scanner severity must be validated and contextualized.
- ✗
Exploit the service by enabling it first.
Why it's wrong here
Changing service state to create exploitability is not appropriate unless explicitly authorized.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume any scanner-reported critical finding must be reported as-is, ignoring the penetration tester's duty to validate and contextualize findings based on actual service state and reachability.
Detailed technical explanation
How to think about this question
In vulnerability management, the Common Vulnerability Scoring System (CVSS) includes environmental metrics like 'Modified Attack Vector' and 'Modified Exploitability' to adjust risk when a service is not reachable. For example, a scanner might flag CVE-2021-44228 (Log4Shell) on a server, but if the vulnerable Log4j library is only present in a disabled service like an unused Apache Tomcat instance, the actual risk is reduced because no network-based attack vector exists. Real-world scenarios often involve legacy software remnants that are not actively exploitable but must be documented for remediation to prevent future exposure.
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: Report the finding with contextual risk adjustment and explain that the vulnerable service is disabled and not reachable. — Option A is correct because the vulnerability scanner identified a real package vulnerability, but manual verification revealed the service is disabled and unreachable. The tester must report the finding with a contextual risk adjustment to accurately reflect the reduced exploitability, as per standard risk assessment practices in penetration testing. This ensures the organization understands the actual risk without ignoring the presence of the vulnerable package, which could be enabled in the future.
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 →
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.