[Developer] Step Functions

Question 1

What is the primary purpose of AWS Step Functions?

Answer 1

To coordinate multiple AWS services into serverless workflows (known as state machines), managing application state, retries, and error handling.

AWS Step Functions simplifies the process of building complex applications by allowing developers to define workflows visually.

Question 2

What are the two main types of AWS Step Functions?

Answer 2

• Standard Workflows (ideal for long-running, durable, and auditable processes)
• Express Workflows (ideal for high-volume, short-duration, and event-driven tasks)

Each type serves different use cases based on workflow duration and processing needs.

Question 3

What is the maximum duration for a Standard Workflow?

Answer 3

1 year

This allows for extensive processes that require long-term execution.

Question 4

What is the maximum duration for an Express Workflow?

Answer 4

5 minutes

This is suitable for quick, event-driven tasks.

Question 5

What is the fundamental building block of an SFN state machine?

Answer 5

A State, defined in a JSON-based Amazon States Language (ASL).

States represent the various steps in a workflow.
Examples include Task, Choice, Wait, Succeed, and Fail.

Question 6

In Step Funtions

What does the Task state do?

Answer 6

It performs work by calling an AWS service API

• Task states are essential for executing specific actions within the workflow.
• Examples of calling service APIs include invoking a Lambda function or starting a Fargate task.

Question 7

How do you handle branching logic (if/then/else) within a Step Functions workflow?

Answer 7

Use the Choice state.

The Choice state allows for conditional execution based on input.

Question 8

How can Step Functions pause a workflow for a specific period of time?

Answer 8

Use the Wait state.

This state allows for delays in the workflow execution.

Question 9

Which SFN feature allows a state to retry a failed task a defined number of times?

Answer 9

A Retrier field configured on a Task state, often utilizing exponential backoff and jitter.

This feature helps to manage transient errors effectively.

Question 10

Which SFN feature allows you to handle expected failures by redirecting the workflow to a cleanup or notification state?

Answer 10

A Catcher field configured on a Task state.

This allows for graceful error handling in workflows.

Question 11

What SFN feature allows a task to wait for an external service (like a human approval) to complete before proceeding?

Answer 11

Callback Patterns using a Task Token, where the external service sends the token back to Step Functions upon completion.

This is useful for workflows that require human intervention.

Question 12

How do you ensure that multiple parallel tasks are all completed before the workflow moves to the next state?

Answer 12

Use the Parallel state, which executes branches concurrently and waits for the results of all branches to merge.

This state is crucial for optimizing workflow execution time.

Question 13

When should you choose Express Workflows over Standard Workflows?

Answer 13

1. For high-rate event processing (e.g., streaming data transformation)
2. when the process needs to complete quickly (under 5 minutes) and intermediate execution history is not strictly required.

This choice is based on the specific needs of the application.