Quick Answer
The answer is to conduct a root cause analysis and implement corrective actions. This is the most appropriate action because a key risk indicator (KRI) that has exceeded its threshold for three consecutive months signals a persistent risk condition, not a temporary spike or data anomaly; without identifying the underlying driver, the risk will continue to erode the control environment. On the Certified in Risk and Information Systems Control CRISC exam, this scenario tests your understanding of the Risk and Control Monitoring and Reporting domain, where proactive remediation is favored over passive observation or simply resetting the threshold. A common trap is to choose "escalate to management" or "adjust the KRI baseline," but the exam expects you to recognize that a sustained breach demands investigative action first. Memory tip: think "Three strikes, dig deep"—three months of breach means it is time to find the root cause, not just report the symptom.
This CRISC practice question tests your understanding of risk and control monitoring and reporting. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 company's risk monitoring report shows that a key risk indicator (KRI) has exceeded the threshold for three consecutive months. What is the MOST appropriate action?
Conduct a root cause analysis and implement corrective actions.
Addresses the cause of the KRI breach.
Wait for the KRI to return to normal on its own.
Why wrong: Passive approach may lead to escalation.
Raise the threshold to avoid future breaches.
Why wrong: Does not address the underlying risk.
Implement temporary manual controls.
Why wrong: May be needed, but root cause analysis is primary.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Conduct a root cause analysis and implement corrective actions.
A KRI that has exceeded its threshold for three consecutive months indicates a persistent risk condition, not a transient anomaly. The most appropriate action is to conduct a root cause analysis to identify the underlying issue and implement corrective actions to bring the risk back within acceptable levels. This aligns with the CRISC domain of Risk and Control Monitoring and Reporting, which emphasizes proactive remediation over passive observation or threshold manipulation.
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.
Conduct a root cause analysis and implement corrective actions.
Why this is correct
Addresses the cause of the KRI breach.
Related concept
Read the scenario before looking for a memorised answer.
Wait for the KRI to return to normal on its own.
Why it's wrong here
Passive approach may lead to escalation.
Raise the threshold to avoid future breaches.
Why it's wrong here
Does not address the underlying risk.
Implement temporary manual controls.
Why it's wrong here
May be needed, but root cause analysis is primary.
Common exam traps
The trap here is that candidates may confuse a persistent KRI breach with a temporary spike and choose to wait (Option B) or adjust the threshold (Option C), failing to recognize that the CRISC framework mandates investigation and corrective action for sustained deviations.
Detailed technical explanation
In practice, KRIs are often tied to specific control effectiveness metrics, such as the number of unpatched critical vulnerabilities exceeding a threshold of 5 for 30 days. A three-month breach suggests a systemic failure in the patch management process, requiring a root cause analysis that might reveal inadequate scanning frequency, resource constraints, or misconfigured automation. Real-world scenarios include financial services where a KRI for failed transaction reconciliations exceeding 2% for three months triggered a review that uncovered a software bug in the reconciliation engine, leading to a permanent fix rather than temporary workarounds.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the CRISC exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Risk and Control Monitoring and Reporting — study guide chapter
Learn the concepts, then practise the questions
Risk and Control Monitoring and Reporting practice questions
Targeted practice on this topic area only
All CRISC questions
500 questions across all exam domains
Certified in Risk and Information Systems Control CRISC study guide
Full concept coverage aligned to exam objectives
CRISC 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 CRISC questions linked to IT Risk Identification.
Practise CRISC questions linked to Risk Response and Mitigation.
Practise CRISC questions linked to Risk and Control Monitoring and Reporting.
Practise CRISC questions linked to IT Risk Assessment.
Practise CRISC questions linked to CRISC fundamentals.
Practise CRISC questions linked to CRISC scenario.
Practise CRISC questions linked to CRISC troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Risk and Control Monitoring and Reporting — This question tests Risk and Control Monitoring and Reporting — Read the scenario before looking for a memorised answer..
The correct answer is: Conduct a root cause analysis and implement corrective actions. — A KRI that has exceeded its threshold for three consecutive months indicates a persistent risk condition, not a transient anomaly. The most appropriate action is to conduct a root cause analysis to identify the underlying issue and implement corrective actions to bring the risk back within acceptable levels. This aligns with the CRISC domain of Risk and Control Monitoring and Reporting, which emphasizes proactive remediation over passive observation or threshold manipulation.
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 →
Last reviewed: Jun 11, 2026
This CRISC practice question is part of Courseiva's free ISACA 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 CRISC 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.