COBIT 2019 Foundation case studies
COBIT 2019 Foundation · Put your knowledge to work in context.
This independent study page provides practice for COBIT 2019 Foundation. Its editorial learning areas include COBIT2019 governance, value and tailored systems; COBIT objectives, capability and implementation evidence; Cyber-risk identification and analysis; Security operations, monitoring and response; Continuity, backup and technical recovery. The questions develop subject knowledge and application through worked reasoning, distinctions between competing answers, and practical scenarios. Study the relevant guide before attempting a mixed set, then explain the evidence or calculation that supports each answer. The COBIT 2019 Foundation case studies are 4 cases and about 819 words.
1A completed deployment has not delivered its intended benefit
A fictional enterprise completes a technology deployment within the approved schedule and purchase budget. The business case expected a reduction in customer waiting time, but supplied service measurements show no improvement and the benefit owner has not reviewed the process changes needed outside IT.
171 words, under 1 min2A control comparison with explicit effectiveness and uncertainty
A fictional organization estimates the value exposed by one defined incident scenario at five hundred thousand currency units and the fraction lost in one successful incident at forty percent. Its classroom model estimates an annualized incident rate of one half, and the exercise asks for expected annual loss rather than a prediction that exactly half an incident occurs each year.
206 words, about 1 min3An incident review with an action that can be checked
A fictional delivery team restores service after a release encounters an undocumented database dependency. The initial meeting ends with the statement that the engineer should be more careful, but no owner, test or review date is recorded.
219 words, about 1 min4A recovery target does not prescribe one universal architecture
A fictional order service has a recovery-point objective of fifteen minutes and a recovery-time objective of four hours. A tested option creates consistent recovery points every ten minutes and restores the service in three hours after the declared recovery procedure begins.
223 words, about 1 min