SAA-C03 Practice Question 56: Step Functions Orchestration

Step Functions is the managed orchestrator for precisely this shape of problem. The seven functions become Task states in a state machine, so the workflow itself holds the execution state instead of a hand-written DynamoDB table. Retry handles transient failures declaratively and Catch routes a permanent failure to a compensating branch, replacing the custom rerun code. A Standard workflow keeps a full execution history that the console renders as a diagram, which is the operator visibility the team is missing, and it runs for up to a year with exactly-once execution semantics per step.

Option A does make each hop durable and retryable, but it solves only part of the problem. Seven queues and seven dead-letter queues is more infrastructure, not less custom code, and nothing anywhere records that order 12345 is between step four and step five; the visibility requirement is untouched.

Option C removes the orchestration problem by removing the decomposition. A single function is capped at a 15-minute runtime, a failure at step six reruns steps one through five from scratch, and the exception handling is still code the team writes and maintains.

Option D swaps direct invocation for a topic but keeps the chain. SNS is fire-and-forget pub/sub with no notion of a workflow, no place to hold state between steps, and no end-to-end view of an order, so the operators are no better off than they are today.

Reference: What is Step Functions?