Which element is essential to a robust backout plan for a production change in FOSSE?

• A. Pre-approved rollback steps
• B. A randomized rollback attempt
• C. No backups
• D. A vague rollback plan

Answer: (A)

Having a robust backout plan hinges on having pre-approved rollback steps. When the rollback steps are approved in advance, there is a clear, repeatable set of actions that the on-call team can follow exactly if something goes wrong with a production change. This minimizes reaction time, reduces ambiguity, and ensures everyone knows their role, the order of operations, and the criteria for deeming the rollback successful. In a FOSSE environment, where changes can impact critical front-office processes, this readiness supports data integrity, minimizes downtime, and preserves trust with users and stakeholders.

In contrast, attempting a rollback randomly introduces variability and unpredictability, which can exacerbate issues rather than resolve them. Not having backups makes a rollback even more fragile, because there may be no reliable way to restore systems or data to a known good state. A vague rollback plan leaves teams guessing during an outage, leading to delays and potential mistakes.