What is a sanity check in CSOSS operations?

• A. A full diagnostic of all subsystems.
• B. A quick verification to ensure data, status, and actions are plausible and safe before proceeding.
• C. A check only after actions are completed.
• D. A verification that uses external data.

Answer: (B)

Sanity checks in CSOSS operations are quick verifications that the data you’re seeing, the system status, and the planned actions all look plausible and safe before you proceed. This step is fast and high-level, aimed at catching obvious inconsistencies or potentially dangerous commands so you don’t advance with something unsafe. It’s not about doing an in-depth diagnostic of every subsystem, and it happens before actions are taken to prevent mistakes, rather than after the fact. If a sensor value is physically impossible or a commanded action would push a system beyond safe limits, the sanity check flags it and stops the step.