Key points

• State machines make coordination and execution history explicit.
• Retry and Catch behavior belongs around the state or integration that can fail.
• Workflow input and output transformations should preserve only the state needed by later steps.

Best-known use cases

• Multi-step application workflows with visible branches and failure handling.
• Orchestrated service integrations across asynchronous or long-running steps.

What candidates often confuse it with

• Step Functions orchestrates explicit workflow state; EventBridge supports event-driven choreography and routing.
• A workflow retry is not a replacement for idempotent application-side effects.

Key takeaway

Choose Step Functions when sequence, state, branching, and recovery must be explicit and observable.

Related services

• Amazon EventBridge
• AWS Lambda
• Amazon SQS

Relevant exam tasks

• D1.1 — Develop code for applications hosted on AWS
• 1.1.1 — Describe architectural patterns (for example, event-driven, microservices, monolithic, choreography, orchestration, fanout)
• 1.1.5 — Create fault-tolerant and resilient applications in a programming language (for example, Java, C#, Python, JavaScript, TypeScript, Go)
• D3.4 — Deploy code by using AWS Continuous Integration and Continuous Delivery (CI/CD) services
• 3.4.7 — Use orchestrated workflows to deploy code to different environments

Learn more

• AWS Step Functions