Quick Answer
The answer is to document evidence that the affected feature or code path is not reachable, along with the approval and rationale for the severity change. This is correct because a critical vulnerability only poses a real risk if the vulnerable code can be executed; if the feature is disabled, the attack surface is effectively closed, so the analyst must prove the feature is unreachable to justify the downgrade. On the CompTIA CySA+ CS0-003 exam, this tests your understanding of risk management and the importance of maintaining an accurate risk register—a common trap is assuming a disabled feature automatically means no risk, but you must still document the technical proof and the change management approval to ensure a clear audit trail. Remember the mnemonic “Proof and Permit”: you need proof the code path is blocked, and a permit (approval) to change the severity.
This CS0-003 practice question tests your understanding of vulnerability management. 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 appears critical but the vulnerable feature is disabled. What should the analyst document before downgrading? (Choose two.)
Approval and rationale for the severity change
Governed downgrades need documented justification.
Deletion of the original scanner finding
Why wrong: Deleting evidence breaks auditability.
The analyst's personal preference for fewer tickets
Why wrong: Preference is not risk evidence.
Evidence that the affected feature or code path is not reachable
Reachability evidence supports risk adjustment.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Approval and rationale for the severity change
Option A is correct because when a vulnerability is critical but the vulnerable feature is disabled, the analyst must document the approval and rationale for the severity change to maintain an accurate risk register and audit trail. This ensures that the decision to downgrade is justified, traceable, and compliant with organizational change management policies, preventing arbitrary adjustments that could obscure true risk posture.
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.
Approval and rationale for the severity change
Why this is correct
Governed downgrades need documented justification.
Related concept
Read the scenario before looking for a memorised answer.
Deletion of the original scanner finding
Why it's wrong here
Deleting evidence breaks auditability.
The analyst's personal preference for fewer tickets
Why it's wrong here
Preference is not risk evidence.
Evidence that the affected feature or code path is not reachable
Why this is correct
Reachability evidence supports risk adjustment.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Cisco often tests the misconception that deleting or ignoring a scanner finding is acceptable when a vulnerability is not exploitable, but the correct approach is to document the rationale and obtain approval for a severity downgrade while preserving the finding for audit and compliance purposes.
Detailed technical explanation
In vulnerability management workflows, severity scoring (e.g., CVSS v3.1 base score) is calculated from intrinsic characteristics of the vulnerability, but environmental and temporal metrics can modify the score to reflect the actual risk in a specific deployment. When a vulnerable feature is disabled, the analyst should apply an environmental metric adjustment (e.g., setting the 'Modified Attack Vector' or 'Modified Scope' to reflect the disabled state) rather than simply deleting or ignoring the finding, ensuring the CVSS score accurately represents the residual risk.
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.
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 — Read the scenario before looking for a memorised answer..
The correct answer is: Approval and rationale for the severity change — Option A is correct because when a vulnerability is critical but the vulnerable feature is disabled, the analyst must document the approval and rationale for the severity change to maintain an accurate risk register and audit trail. This ensures that the decision to downgrade is justified, traceable, and compliant with organizational change management policies, preventing arbitrary adjustments that could obscure true risk posture.
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 →
Keep practising
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.