Practice essential collocations for incident retrospectives in IT and software development.
0 / 5 completed
1 / 5
After the outage, the SRE team held a blameless review to ___ the root cause of the failure.
Identify the root cause is the standard incident management collocation for determining the underlying reason a failure occurred. 'Find along' and 'spot around' are informal. 'Dig out' is too casual for a formal post-incident review.
2 / 5
The on-call engineer was asked to ___ a timeline of events so the team could understand how the incident unfolded.
Reconstruct a timeline is the standard incident retrospective collocation for piecing together the sequence of events from logs and observations. 'Build along' and 'make around' are informal. 'Draw out' does not convey the precise reconstruction required.
3 / 5
The retrospective produced a list of action items designed to ___ the likelihood of a similar incident recurring.
Reduce the likelihood is the standard risk and incident collocation for lessening the probability of an undesirable event. 'Lower along' and 'cut around' are informal. 'Drop out' has a different meaning and does not fit this context.
4 / 5
The incident commander made sure the team would ___ lessons from the failure and update the relevant runbooks.
Capture lessons is the standard retrospective collocation for recording the insights gained from an incident so they are not lost. 'Take along' and 'grab around' are informal. 'Note out' is not a standard phrase in this context.
5 / 5
The team agreed to ___ follow-up actions to specific owners with clear deadlines after the review.
Assign actions is the standard project and incident management collocation for allocating responsibility for follow-up tasks. 'Give along' and 'hand around' are informal. 'Put out' has different meanings and does not fit this context.