Which option describes a way to validate flow rollback behavior?

Which option describes a way to validate flow rollback behavior?

• A. Test a flow with rollback
• B. Deploy to production
• C. Run a performance test
• D. Create a test data set

Answer: (A)

Testing how a flow handles rollback requires proving that, if an error occurs, the changes the flow made are undone and the system returns to its pre-flow state. To validate this, run the flow in a controlled test and deliberately trigger a failure along the path; you should observe that any updates performed before the failure are rolled back and no partial changes remain. This directly exercises the rollback mechanism and confirms data integrity after errors. Deploying to production carries risk and isn’t a test of rollback, performance testing measures speed rather than rollback behavior, and merely creating a test data set, while useful for input coverage, doesn’t verify that rollback works as intended.

Testing how a flow handles rollback requires proving that, if an error occurs, the changes the flow made are undone and the system returns to its pre-flow state. To validate this, run the flow in a controlled test and deliberately trigger a failure along the path; you should observe that any updates performed before the failure are rolled back and no partial changes remain. This directly exercises the rollback mechanism and confirms data integrity after errors. Deploying to production carries risk and isn’t a test of rollback, performance testing measures speed rather than rollback behavior, and merely creating a test data set, while useful for input coverage, doesn’t verify that rollback works as intended.