Step Functions for workflows in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is AWS Step Functions?

AWS Step Functions is a service that helps you coordinate multiple tasks into a workflow. It makes sure each step happens in order and handles errors automatically.

beginner

What is a state in Step Functions?

A state is a single step in a workflow. It can do things like run a task, wait, choose between paths, or end the workflow.

intermediate

How does Step Functions handle errors in workflows?

Step Functions can catch errors and retry steps or move to a different path. This helps workflows keep running smoothly even if something goes wrong.

intermediate

What is the difference between a Task state and a Choice state?

A Task state runs a job like calling a Lambda function. A Choice state decides which path to take next based on conditions.

beginner

Why use Step Functions instead of writing code to manage workflows?

Step Functions makes workflows visual and easier to manage. It handles retries, errors, and state tracking automatically, saving time and reducing mistakes.

What does a Task state in Step Functions do?

A Runs a job like a Lambda function

B Makes a decision between paths

C Waits for a set time

D Ends the workflow

A Task state runs a job such as invoking a Lambda function or other AWS service.

Which state type lets you choose the next step based on conditions?

A Task

B Wait

C Choice

D Pass

Choice states evaluate conditions and decide which path to follow next.

How does Step Functions help with errors in workflows?

A It retries or routes to error handling steps

B It sends an email only

C It ignores errors

D It stops the workflow immediately

Step Functions can retry failed steps or move to error handling states to keep workflows running.

What is the main benefit of using Step Functions?

A Writing complex code for workflows

B Visualizing and managing workflows easily

C Replacing all AWS services

D Storing large files

Step Functions provides a visual way to build and manage workflows, simplifying orchestration.

Which state type pauses the workflow for a set time?

A Fail

B Task

C Choice

D Wait

Wait states pause the workflow for a specified duration or until a time.

Explain how AWS Step Functions help manage complex workflows.

Think about how Step Functions make many steps work together smoothly.

Describe the role of different state types in Step Functions workflows.

Consider what each step in a workflow can do.

Practice

1. What is the main purpose of AWS Step Functions in a workflow?

easy

A. To monitor network traffic between AWS services

B. To coordinate and manage the sequence of tasks in a workflow

C. To provide a user interface for AWS services

D. To store large amounts of data for applications

Solution

1. Step 1: Understand the role of Step Functions

   AWS Step Functions help organize and control the order of tasks in a workflow, making sure each step runs in sequence or parallel as needed.

2. Step 2: Compare with other AWS services

   Other options describe storage, UI, or monitoring, which are not the main functions of Step Functions.

3. Final Answer:

   To coordinate and manage the sequence of tasks in a workflow -> Option B

4. Quick Check:

   Step Functions = task coordination [OK]

Hint: Step Functions organize tasks step-by-step [OK]

Common Mistakes:

• Confusing Step Functions with storage services
• Thinking Step Functions provide UI
• Assuming Step Functions monitor network traffic

2. Which JSON field is required to define a task state in an AWS Step Functions state machine?

easy

A. "Timeout" specifying the maximum execution time

B. "Retry" specifying the retry policy

C. "InputPath" specifying the input data format

D. "Resource" specifying the ARN of the task to run

Solution

1. Step 1: Identify the key field for task execution

   The "Resource" field is mandatory in a task state to specify which AWS service or Lambda function to invoke.

2. Step 2: Understand other fields

   "Timeout", "InputPath", and "Retry" are optional fields that control behavior but are not required to define a task.

3. Final Answer:

   "Resource" specifying the ARN of the task to run -> Option D

4. Quick Check:

   Task state needs "Resource" [OK]

Hint: "Resource" points to the task to run [OK]

Common Mistakes:

• Confusing optional fields with required ones
• Using "Timeout" as a required field
• Forgetting to specify the task ARN

3. Given this Step Functions snippet, what is the next state after TaskA completes successfully?

{
  "StartAt": "TaskA",
  "States": {
    "TaskA": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:region:123456789012:function:FunctionA",
      "Next": "TaskB"
    },
    "TaskB": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:region:123456789012:function:FunctionB",
      "End": true
    }
  }
}

medium

A. TaskB

B. TaskA

C. End state

D. No next state defined

Solution

1. Step 1: Read the "Next" field of TaskA

   The JSON shows "Next": "TaskB" for TaskA, meaning after TaskA finishes, the workflow moves to TaskB.

2. Step 2: Confirm TaskB is defined

   TaskB is defined and marked with "End": true, so it is the final step after TaskA.

3. Final Answer:

   TaskB -> Option A

4. Quick Check:

   TaskA's "Next" = TaskB [OK]

Hint: Check the "Next" field for the following state [OK]

Common Mistakes:

• Assuming TaskA loops to itself
• Thinking workflow ends after TaskA
• Ignoring the "Next" field

4. You have this Step Functions state definition:

{
  "Type": "Task",
  "Resource": "arn:aws:lambda:region:123456789012:function:MyFunction",
  "Next": "NextState"
}

What is missing that could cause a failure if the Lambda function errors?

medium

A. "Catch" block to handle errors

B. "TimeoutSeconds" field to limit execution time

C. "ResultPath" to store output

D. "StartAt" field to define the first state

Solution

1. Step 1: Identify error handling in Step Functions

   Without a "Catch" block, errors from the Lambda function cause the workflow to fail immediately.

2. Step 2: Understand other fields

   "TimeoutSeconds" limits time but is optional; "ResultPath" controls output storage; "StartAt" is for the state machine root, not individual states.

3. Final Answer:

   "Catch" block to handle errors -> Option A

4. Quick Check:

   Error handling needs "Catch" [OK]

Hint: Add "Catch" to handle task errors safely [OK]

Common Mistakes:

• Confusing "TimeoutSeconds" with error handling
• Omitting "Catch" causes workflow failure on error
• Thinking "StartAt" is needed inside a task

5. You want to build a workflow that runs two Lambda functions in parallel and then proceeds only when both finish successfully. Which Step Functions state type should you use?

hard

A. Map state

B. Choice state

C. Parallel state

D. Pass state

Solution

1. Step 1: Understand the requirement for parallel execution

   Running two Lambda functions at the same time and waiting for both to finish requires a "Parallel" state.

2. Step 2: Review other state types

   "Choice" is for branching decisions, "Map" is for iterating over items, and "Pass" passes data without work.

3. Final Answer:

   Parallel state -> Option C

4. Quick Check:

   Parallel state runs tasks simultaneously [OK]

Hint: Use Parallel state to run tasks together [OK]

Common Mistakes:

• Using Choice state for parallelism
• Confusing Map state with parallel execution
• Thinking Pass state runs tasks