A peer check is a deliberate independent verification performed by another qualified person before a consequential operational step , so A is correct. The objective is to identify mistakes before they alter equipment state, affect redundancy, create a safety exposure, or disrupt service.
In critical-facilities work, peer verification may be applied before switching electrical equipment, manipulating valves, executing critical procedure steps, confirming equipment identifiers, or making other changes where human error could have significant consequences. It functions as a human-performance barrier rather than as a substitute for the written procedure.
Oracle Data Center Operations Foundations is explicitly described as a safety-first, procedures-based curriculum and requires learners to follow standard and emergency procedures, use technical documentation, recognize operational conditions, and demonstrate professional behavior. These principles support deliberate verification controls for critical actions.
B is a handover/documentation function rather than peer checking. C is an automated validation mechanism and therefore does not involve a second person. D occurs after work and therefore cannot prevent an incorrect critical action.
A proper peer check should occur before the point of consequence , with both individuals confirming the required component, intended action, procedure step, and expected result.
===============