Question 330 of 509
Reporting and CommunicationmediumMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to include it as a recurring finding and explicitly note the lack of remediation. This is required because penetration testing standards like PTES and OWASP mandate that any previously reported vulnerability that remains unpatched must be documented as a recurring finding, with a direct reference to the prior report, to accurately reflect the persistent risk. On the CompTIA PenTest+ PT0-002 exam, this tests your understanding of proper reporting procedures and risk communication, often appearing as a trap where candidates might mistakenly recommend re-testing only or omitting the finding. A common memory tip is to think of the “recurring” label as a red flag that forces the client to track remediation progress over time, ensuring compliance with frameworks like NIST SP 800-115. Remember the mnemonic: “Re-report, don’t re-test alone.”

PT0-002 Reporting and Communication Practice Question

This PT0-002 practice question tests your understanding of reporting and communication. 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 penetration tester discovers that a previously reported vulnerability from a prior test has not been remediated. How should this be communicated in the current report?

Question 1mediummultiple choice
Full question →

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

Include it as a recurring finding and note the lack of remediation.

Option B is correct because penetration testing standards (e.g., PTES, OWASP) require that previously identified vulnerabilities that remain unpatched be documented as recurring findings with explicit reference to the prior report. This ensures the client understands the risk persists and can track remediation progress over time. Including the finding with a note on lack of remediation maintains the integrity of the current risk assessment and supports compliance with reporting frameworks like NIST SP 800-115.

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.

  • Only mention it in the executive summary, referencing the past report.

    Why it's wrong here

    Detailed findings should be in the technical section.

  • Include it as a recurring finding and note the lack of remediation.

    Why this is correct

    This provides accountability and highlights the need for action.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Omit the finding to avoid repetition.

    Why it's wrong here

    Recurring vulnerabilities are important to track.

  • Reduce the severity rating because it was already reported.

    Why it's wrong here

    Severity should be based on current risk, not prior reporting.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates mistakenly think repeating a finding is redundant or that the executive summary is sufficient, but CompTIA expects the finding to be fully documented in the technical body of the report with a clear note on recurrence.

Detailed technical explanation

How to think about this question

Under the hood, a recurring finding should include the original CVE or finding ID, the date of first discovery, and a comparison of current vs. previous evidence (e.g., same open port, same vulnerable service banner). In real-world scenarios, clients often use these recurring entries to demonstrate due diligence to auditors or regulators, so the report must clearly state that the vulnerability was previously reported and remains unmitigated. This also helps the penetration tester avoid accusations of negligence if the same vulnerability is later exploited.

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.

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.

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?

Reporting and Communication — This question tests Reporting and Communication — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Include it as a recurring finding and note the lack of remediation. — Option B is correct because penetration testing standards (e.g., PTES, OWASP) require that previously identified vulnerabilities that remain unpatched be documented as recurring findings with explicit reference to the prior report. This ensures the client understands the risk persists and can track remediation progress over time. Including the finding with a note on lack of remediation maintains the integrity of the current risk assessment and supports compliance with reporting frameworks like NIST SP 800-115.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 25, 2026

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.

Loading comments…

Sign in to join the discussion.

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.