In fault-tolerant robot software, what is the purpose of a fallback routine?

• A. To ignore the fault and keep operating.
• B. To provide a safe, predefined response when a failure occurs.
• C. To automatically replace hardware when possible.
• D. To shutdown whenever any fault is detected.

Answer: (B)

The idea being tested is how a fault-tolerant system responds to problems with a controlled, safe action. A fallback routine defines a predefined set of steps the robot takes when a failure is detected, aiming to keep people safe and the system from getting into a dangerous state. It often involves entering a safe mode, stopping or limiting motion, reducing speed, and possibly alerting operators, so the robot degrades gracefully rather than reacting unpredictably. This is not about ignoring the fault or continuing as if nothing happened, which would risk worsening the situation. It’s also not about automatically swapping hardware, which is a maintenance or repair action outside the scope of software fallback behavior. Nor is it about always shutting down on any fault, which would be overly conservative and impractical in many scenarios. Therefore, the purpose of a fallback routine is to provide a safe, predefined response when a failure occurs.