Quick Answer
The answer is that vulnerability closure requires a retest showing the vulnerability is gone. This is because remediation cannot be considered complete without objective evidence that the specific vulnerable condition—such as a missing patch, misconfiguration, or outdated library—has been fully resolved. A retest, whether automated or manual, directly confirms the absence of the flaw, aligning with frameworks like NIST SP 800-115 and PCI DSS 11.3.2 that mandate verification before closure. On the CompTIA CySA+ CS0-003 exam, this concept tests your understanding of the vulnerability management lifecycle and the critical difference between “fixing” and “verifying.” A common trap is assuming a patching report alone suffices; the exam emphasizes that only a retest provides the required proof. For tool configuration, the most direct improvement to result quality is enabling authenticated scanning or integrating a vulnerability scanner into the CI/CD pipeline to catch regressions automatically. Memory tip: “Patch it, then prove it—no retest, no rest.”
This CS0-003 practice question tests your understanding of vulnerability management. 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. A key principle to apply: vulnerability closure requires validation evidence.. 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 team says a critical vulnerability was patched. What should the vulnerability manager require before closure? For tool configuration, Which scanner or pipeline change most directly improves result quality?
Wait one year before testing
Why wrong: Delayed validation leaves uncertainty.
Close it immediately based on the email
Why wrong: Claims need verification.
Create a duplicate ticket for every asset
Why wrong: Duplicates create noise and do not prove remediation.
A retest showing the vulnerable condition is no longer present
Closure should be based on validation evidence, not only a remediation claim.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
A retest showing the vulnerable condition is no longer present
Option D is correct because the vulnerability manager must obtain objective evidence that the vulnerability has been remediated. A retest, either automated or manual, confirms that the specific vulnerable condition (e.g., a missing patch, misconfiguration, or outdated library) is no longer present on the asset. This aligns with the NIST SP 800-115 and PCI DSS 11.3.2 requirement for verification of remediation before closure.
Key principle: Vulnerability closure requires validation evidence.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Wait one year before testing
Why it's wrong here
Delayed validation leaves uncertainty.
Close it immediately based on the email
Why it's wrong here
Claims need verification.
Create a duplicate ticket for every asset
Why it's wrong here
Duplicates create noise and do not prove remediation.
A retest showing the vulnerable condition is no longer present
Why this is correct
Closure should be based on validation evidence, not only a remediation claim.
Related concept
Vulnerability closure requires validation evidence.
Common exam traps
Cisco often tests the misconception that a verbal or written claim of a patch is sufficient, but the correct answer always requires technical verification via a retest or rescan.
Detailed technical explanation
Under the hood, a retest typically involves running the same scanner plugin or check that originally detected the vulnerability, but now expecting a 'pass' or 'not vulnerable' result. For example, if the vulnerability was CVE-2023-44487 (HTTP/2 Rapid Reset), the scanner would verify that the web server no longer accepts vulnerable HTTP/2 frames or that the patch has been applied. In real-world scenarios, a partial patch or misconfigured firewall rule can leave the vulnerability exploitable, so a retest on the exact same asset with the same credentials is critical.
Key takeaway
Vulnerability closure requires validation evidence.
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
Review vulnerability closure requires validation evidence., then practise related CS0-003 questions on the same topic to reinforce the concept.
Vulnerability Management — study guide chapter
Learn the concepts, then practise the questions
Vulnerability Management practice questions
Targeted practice on this topic area only
All CS0-003 questions
503 questions across all exam domains
CompTIA CySA+ CS0-003 study guide
Full concept coverage aligned to exam objectives
CS0-003 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 CS0-003 questions linked to Security Operations.
Practise CS0-003 questions linked to Vulnerability Management.
Practise CS0-003 questions linked to Incident Response and Management.
Practise CS0-003 questions linked to Reporting and Communication.
Practise CS0-003 questions linked to CompTIA A+ hardware.
Practise CS0-003 questions linked to CompTIA A+ mobile devices.
Practise CS0-003 questions linked to CompTIA A+ networking.
Practise CS0-003 questions linked to CompTIA A+ operating systems.
Practise CS0-003 questions linked to CompTIA A+ security.
Practise CS0-003 questions linked to CompTIA A+ software troubleshooting questions.
Practise CS0-003 questions linked to CompTIA A+ operational procedures questions.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Vulnerability Management — This question tests Vulnerability Management — Vulnerability closure requires validation evidence..
The correct answer is: A retest showing the vulnerable condition is no longer present — Option D is correct because the vulnerability manager must obtain objective evidence that the vulnerability has been remediated. A retest, either automated or manual, confirms that the specific vulnerable condition (e.g., a missing patch, misconfiguration, or outdated library) is no longer present on the asset. This aligns with the NIST SP 800-115 and PCI DSS 11.3.2 requirement for verification of remediation before closure.
Review vulnerability closure requires validation evidence., then practise related CS0-003 questions on the same topic to reinforce the concept.
Vulnerability closure requires validation evidence.
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 →
Same concept, more angles
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A team says a critical vulnerability was patched. What should the vulnerability manager require before closure? For stakeholder management, Which documentation or approval is required to keep the programme defensible?
hardWhy C: Option C is correct because the vulnerability manager must obtain objective evidence that the vulnerability has been remediated before closing the finding. An email assertion is insufficient; a retest (manual or automated) confirming the vulnerable condition is no longer present provides the verifiable proof required for closure and defensible stakeholder reporting.
Variation 2. A team says a critical vulnerability was patched. What should the vulnerability manager require before closure? For validation, Which action should be taken before closing or downgrading the finding?
hardWhy B: Option B is correct because the vulnerability manager must obtain objective evidence that the fix was successfully applied and the vulnerability is no longer exploitable. A retest—typically performed via authenticated scanning or manual verification—confirms the absence of the vulnerable condition, aligning with the remediation validation phase in the vulnerability management lifecycle. Closing based solely on a team's email (Option C) violates the principle of verify, not trust, and could leave residual risk unaddressed.
Variation 3. A team says a critical vulnerability was patched. What should the vulnerability manager require before closure? For business prioritization, Which recommendation gives the best risk-based order of work?
hardWhy A: A retest is required to confirm that the vulnerability has been successfully remediated. Without a retest, the vulnerability manager cannot verify that the patch was applied correctly or that it did not introduce new issues. This aligns with the vulnerability management lifecycle, where closure is only granted after a validated scan or manual test shows the vulnerable condition is eliminated.
Last reviewed: Jun 11, 2026
This CS0-003 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 CS0-003 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.