hardMultiple Choice
Risk Acceptance Documentation for CompTIA CySA+
A business owner accepts delayed remediation for a production system. What must the report include? If the primary audience is executive leadership, which content choice is most appropriate?
Quick Answer
The answer is risk owner, reason, compensating controls, review date, and expiry. This set of elements is required because risk acceptance documentation must ensure that a formally accepted risk is not permanently ignored; it demands accountability through the named risk owner, a clear justification for the delay, the compensating controls that reduce the current exposure, and a scheduled review and expiry date to force re-evaluation. On the CompTIA CySA+ CS0-003 exam, this concept tests your understanding of the risk management lifecycle and how to communicate residual risk to executive leadership, who need a concise, actionable summary rather than technical details. A common trap is omitting the expiry or review date, which would allow the risk to drift into indefinite acceptance. Remember the mnemonic "ORCE" — Owner, Reason, Controls, Expiry — to lock in the five required fields.
⚠ Common exam trap
The CS0-004 exam often tests the misconception that risk acceptance can be permanent or that a single opinion suffices, but the exam requires documentation of ownership, controls, and a mandatory review/expiry cycle to ensure governance and auditability.
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
✓
Risk owner, reason, compensating controls, review date, and expiry
When a business owner accepts delayed remediation for a production system, the report must formally document the risk owner, the reason for the delay, any compensating controls in place, a scheduled review date, and an expiry date. This ensures accountability, traceability, and that the risk is not permanently ignored, aligning with risk management frameworks like NIST SP 800-37 or ISO 27001.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A permanent exception with no review
Why it's wrong here
A permanent exception with no review removes the time-bound, reassessed nature that accepted risk requires; executive reporting must show a review date and owner. It is tempting because a business owner's acceptance feels final, and permanent exceptions suit genuinely immutable constraints, not a production system whose remediation is merely delayed.
- ✓
Risk owner, reason, compensating controls, review date, and expiry
Why this is correct
Executive leadership needs business-level accountability, not technical detail, so the report must name the risk owner, justify the delay, list compensating controls, and set review and expiry dates. This satisfies the stem's primary-audience constraint by enabling informed risk acceptance decisions.
- ✗
Only the analyst's personal opinion
Why it's wrong here
Executive leadership needs quantified business impact, risk rating and remediation timeline, not the analyst's subjective view, which provides no decision basis and cannot be audited. It is tempting because analysts hold the technical context, and personal opinion is acceptable in informal triage notes, never in formal risk-acceptance reporting.
- ✗
No mention of the accepted risk
Why it's wrong here
Omitting the accepted risk leaves executive leadership unaware of an unresolved production exposure, defeating the report's governance purpose. The report must document the risk, its business impact, and the remediation timeline. Omitting detail suits a purely technical audience already tracking the issue operationally.
Go deeper
Related to this question
Learn chapter
Remediation SLAs and Risk Acceptance
Key term
Risk
Risk is the possibility that an event or action will negatively affect an organization's ability to achieve its goals, often measured in terms of likelihood and impact.
Key term
Remediation
Remediation is the process of fixing or eliminating vulnerabilities, misconfigurations, or security weaknesses in an IT environment.
About these practice questions
One of 701 original CS0-004 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
4 more ways this is tested on CS0-004
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 business owner accepts delayed remediation for a production system. What must the report include? If the primary audience is legal/privacy stakeholder, which content choice is most appropriate?
hard- A.No mention of the accepted risk
- B.Only the analyst's personal opinion
- ✓ C.Risk owner, reason, compensating controls, review date, and expiry
- D.A permanent exception with no review
Why C: When a business owner accepts delayed remediation for a production system, the report must formally document the risk acceptance. This includes the risk owner, the reason for accepting the risk, any compensating controls in place, a review date to reassess the risk, and an expiry date for the acceptance. For a legal/privacy stakeholder, this documentation provides an auditable trail that demonstrates due diligence and compliance with regulatory requirements, such as GDPR or HIPAA.
Variation 2. A business owner accepts delayed remediation for a production system. What must the report include? If the primary audience is business service owner, which content choice is most appropriate?
hard- A.Only the analyst's personal opinion
- ✓ B.Risk owner, reason, compensating controls, review date, and expiry
- C.No mention of the accepted risk
- D.A permanent exception with no review
Why B: When a business owner accepts delayed remediation for a production system, the report must formally document the risk acceptance decision. This includes the risk owner (who accepted the risk), the reason for acceptance, any compensating controls in place, a review date to reassess the risk, and an expiry date for the acceptance. This aligns with risk management frameworks like NIST SP 800-37 and ISO 27005, which require traceability and accountability for accepted risks.
Variation 3. A business owner accepts delayed remediation for a production system. What must the report include? If the primary audience is technical remediation owner, which content choice is most appropriate?
hard- ✓ A.Risk owner, reason, compensating controls, review date, and expiry
- B.No mention of the accepted risk
- C.A permanent exception with no review
- D.Only the analyst's personal opinion
Why A: When a business owner accepts delayed remediation for a production system, the risk acceptance must be formally documented to maintain an accurate risk register and audit trail. The documentation must include the risk owner (who accepted the risk), the reason for the delay, any compensating controls in place to mitigate the risk during the delay, a review date to reassess the risk, and an expiry date to ensure the acceptance does not become permanent. This aligns with risk management frameworks like NIST SP 800-37 and ISO 27005, which require explicit documentation of risk acceptance decisions.
Variation 4. A business owner accepts delayed remediation for a production system. What must the report include? If the primary audience is SOC manager, which content choice is most appropriate?
hard- A.Only the analyst's personal opinion
- B.A permanent exception with no review
- C.No mention of the accepted risk
- ✓ D.Risk owner, reason, compensating controls, review date, and expiry
Why D: When a business owner accepts delayed remediation for a production system, the report must formally document the risk acceptance. This includes the risk owner, the reason for acceptance, any compensating controls in place, a scheduled review date, and an expiry date for the exception. This ensures traceability, accountability, and that the risk is not forgotten, aligning with governance frameworks like NIST SP 800-37 or ISO 27001.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CS0-004 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-004 exam.