How would you answer an interview scenario involving rollback strategy?

In an interview, I would first define rollback strategy and the problem it solves, then explain how I would keep previous artifacts available, use backward-compatible schema changes, automate reversal or traffic switching, define rollback triggers, test the process, and know when roll-forward is safer than reversing data changes. I would also call out the main failure mode: treating rollback as simply redeploying the previous binary fails when the release changed schemas, messages, or data in a non-backward-compatible way. Finally, I would describe how I would test, monitor, and safely roll back or recover the solution.