CIM Change Management & Incident Prevention Flashcards
6 cards from real CIM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 CIM Change Management & Incident Prevention flashcards as text
What is the key distinction between proactive and reactive incident management?
Answer: Proactive management identifies and prevents potential incidents before they impact users
Proactive incident management uses monitoring, trend analysis, and risk assessment to prevent incidents before they occur, while reactive management responds after service is already disrupted.
Which ITSM practice monitors system events to detect warning signs before they escalate into full incidents?
Answer: Event management with threshold alerting
Event management with threshold alerting monitors infrastructure metrics in real-time, enabling teams to detect and respond to warning signs before they escalate into user-impacting incidents.
What is a 'Known Error' in ITIL, and how does it support faster incident resolution?
Answer: A problem with a documented root cause and workaround stored in the Known Error Database (KEDB)
A Known Error is a problem with an identified root cause and documented workaround recorded in the KEDB, enabling faster incident resolution and consistent handling of recurring issues.
How does trend analysis of incident data support proactive incident management?
Answer: It reveals recurring failure patterns that indicate systemic problems requiring preventive action
Trend analysis of incident data reveals recurring failure patterns and systemic weaknesses, enabling problem management to address root causes and prevent future incidents.
Which long-term activity most effectively reduces overall incident frequency in an IT organization?
Answer: Implementing robust problem management to eliminate recurring root causes
A robust problem management process investigates and eliminates root causes of recurring incidents, delivering sustained long-term reduction in incident frequency and severity.
How does a well-maintained CMDB support proactive incident prevention?
Answer: It provides accurate asset and dependency data to identify vulnerable components before they cause incidents
A well-maintained CMDB provides visibility into asset relationships and dependencies, enabling proactive identification of vulnerable or overloaded components before they cause incidents.