Explanation:
A risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives. To ensure that risks are appropriately recorded, they should be documented in a consistent and structured way, such as using a RAID log (Risks, Assumptions, Issues and Dependencies). A RAID log should include information such as the risk description, impact, probability, source, owner, mitigation actions, status and date. Therefore, options B and C are essential for recording risks, as they help to identify where the risk originates from and who is responsible for managing it. Option A is not relevant to recording risks, as it is the name of the tool used to document them. Option D and E are not relevant to recording risks, as they relate to the countermeasures or actions taken to address them, not the risks themselves.
A risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives. To ensure that risks are appropriately recorded, they should be documented in a consistent and structured way, such as using a RAID log (Risks, Assumptions, Issues and Dependencies). A RAID log should include information such as the risk description, impact, probability, source, owner, mitigation actions, status and date. Therefore, options B and C are essential for recording risks, as they help to identify where the risk originates from and who is responsible for managing it. Option A is not relevant to recording risks, as it is the name of the tool used to document them. Option D and E are not relevant to recording risks, as they relate to the countermeasures or actions taken to address them, not the risks themselves.