A county planning office needs a multi-step building-permit workflow that calls inspection, fee, and zoning services in order, retries transient failures, and runs compensating steps if a later stage fails. Which approach best meets reliability and orchestration needs?
Select an answer to reveal the explanation.
Short Explanation
Picture the permit as a relay race with a clipboard that never gets lost. Step Functions keeps that clipboard—retries the dropped baton and runs undo steps when a later leg fails.
Full Explanation
AWS Step Functions provides durable state machines for multi-step workflows, including retries, error catching, and compensating actions when a later stage fails. Synchronous Lambda chaining or queue workers without an orchestrator lose durable progress and compensation semantics. Cron-only scheduling does not track intermediate state or conditional compensations. For reliable municipal permit approvals, Step Functions is the purpose-built integration pattern.