How would you handle a practical scenario involving Saga Pattern in Microservices Architecture?

For a practical scenario involving Saga Pattern, I would first clarify the business goal, scale, constraints, and the failure or quality attribute being tested. A saga coordinates a business transaction across multiple services using a sequence of local transactions and compensating actions. The scenario centers on for order, payment, inventory, and shipping, describe a saga and what happens when payment succeeds but inventory reservation fails. For production, define steps, ownership, timeouts, idempotency, compensating actions, observability, and whether orchestration or choreography best fits the workflow. I would then compare the main alternatives and tradeoffs, identify likely failure modes, and explain how I would validate the solution through testing, observability, security controls, and recovery or rollback planning.