Learn by Novus · Open practice pack v1

Multitasking and monitoring: applied practice: open practice pack: answer key

20 untimed questions across 4 authored sections.

This is untimed educational practice for one applied skill. It is not a clinical, diagnostic, employment, or professionally recognized assessment, it does not produce a score or credential, and for the judgement and safety families it is not a substitute for your employer's own policies, training, or legal duties.

Answer key

ItemChoiceAnswer
multitasking-monitoring-applied-s01-q01AAttend to the drifting gauge now: a consistent trend predicts an exceedance, whereas a steady value is only a snapshot
multitasking-monitoring-applied-s01-q02DAdopt a fixed scan interval, and where possible put an audible alert on the display that is out of view
multitasking-monitoring-applied-s01-q03BThe rarely changing one: detection performance falls sharply when the events being watched for are rare
multitasking-monitoring-applied-s01-q04CDetection performance declines measurably within the first half hour, so breaks, rotation, or automated detection have to be designed in
multitasking-monitoring-applied-s01-q05DTreat the disagreement itself as a fault condition, and get an independent third check before acting on either reading
multitasking-monitoring-applied-s02-q01BTreat the false-alarm rate as a defect in its own right and fix or re-threshold it, because an alarm that cries wolf will be ignored, including the time it is real
multitasking-monitoring-applied-s02-q02CBy the trade it makes: any threshold exchanges missed detections for false alarms, so it is set by the relative cost of the two errors
multitasking-monitoring-applied-s02-q03ALook for a single upstream cause: correlated alarms are usually one event propagating through connected systems
multitasking-monitoring-applied-s02-q04DIt should not be an alarm: reclassify it as an indication, because a non-actionable alarm spends the attention a real one needs
multitasking-monitoring-applied-s02-q05CSilencing removes the sound and not the condition: acknowledge it in the system and keep the condition visible, or it will be forgotten
multitasking-monitoring-applied-s03-q01DNo: what feels like doing both is rapid switching, and every switch costs time and raises the error rate
multitasking-monitoring-applied-s03-q02ABefore you turn away, note where you are and what the next action is
multitasking-monitoring-applied-s03-q03COne well-practised, largely automatic task alongside one demanding task, provided they do not compete for the same input or output channel
multitasking-monitoring-applied-s03-q04BGo back to the last point you can positively verify and redo forward from there
multitasking-monitoring-applied-s03-q05AFinish the current record, then give them your full attention
multitasking-monitoring-applied-s04-q01CRe-rank explicitly against the new conditions, and tell the people who were relying on the previous order
multitasking-monitoring-applied-s04-q02BReport it and have it assessed: normalising an exceedance is how limits stop meaning anything
multitasking-monitoring-applied-s04-q03DHand over the current state, what changed on your shift, outstanding items with owners, and the things you are still unsure about: in person where possible, with the log as the record
multitasking-monitoring-applied-s04-q04AReport it now with the time and what you were doing, because a late report still allows recovery and the gap is itself useful information
multitasking-monitoring-applied-s04-q05BThe job becomes supervising the automation and being able to take over, which is harder to sustain and needs deliberate practice on the manual task