Step Functions for workflows in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when a Step Function state fails without a retry?

Consider an AWS Step Function with a state that fails and has no retry configured. What is the behavior of the workflow?

A The entire workflow immediately fails and stops execution.

B The workflow retries the failed state automatically three times.

C The workflow ignores the failure and continues to the next state.

D The workflow pauses and waits for manual intervention.

💡 Hint

Think about what happens if no retry or catch is set for a failing state.

If a state fails and there is no retry or catch configured, the Step Function workflow stops and is marked as failed immediately.

❓ Architecture

intermediate

Which Step Function state type is best for running a Lambda function asynchronously?

You want to run an AWS Lambda function asynchronously within a Step Function workflow. Which state type should you use?

A Choice state directing to Lambda.

B Wait state before calling Lambda.

C Pass state with Lambda ARN.

D Task state with 'InvocationType' set to 'Event'.

💡 Hint

Consider how to invoke Lambda asynchronously in Step Functions.

Task states can invoke Lambda functions. Setting 'InvocationType' to 'Event' makes the call asynchronous.

❓ security

advanced

How to securely pass sensitive data to a Step Function without exposing it in logs?

You need to pass sensitive information (like passwords) to a Step Function execution but want to avoid exposing it in CloudWatch logs. What is the best practice?

A Store sensitive data in AWS Secrets Manager and reference it in the Step Function using parameters.

B Include sensitive data directly in the input JSON of the Step Function execution.

C Encrypt sensitive data manually and pass as plain text in input.

D Send sensitive data as environment variables in Lambda functions only.

💡 Hint

Think about AWS services designed for secrets management and integration with Step Functions.

Using AWS Secrets Manager to store sensitive data and referencing it in Step Functions keeps secrets out of logs and input payloads.

❓ Configuration

advanced

What is the effect of setting 'HeartbeatSeconds' in a Task state?

In an AWS Step Function Task state, you set 'HeartbeatSeconds' to 30. What happens if the task does not send a heartbeat within 30 seconds?

A The Step Function pauses and waits indefinitely.

B The task automatically retries without failure.

C The Step Function marks the task as failed due to timeout.

D The task continues running without interruption.

💡 Hint

HeartbeatSeconds is related to task health checks.

If a task does not send a heartbeat within the specified time, Step Functions considers it failed and stops the execution.

✅ Best Practice

expert

How to design a Step Function workflow to handle partial failures and continue processing?

You have a Step Function workflow that processes multiple independent tasks. You want the workflow to continue even if some tasks fail, collecting success and failure results. Which design approach achieves this?

A Use Wait states between tasks to avoid failures.

B Use Parallel state with Catch blocks on each branch to handle failures and continue.

C Use Choice states to skip failed tasks without capturing errors.

D Use a single Task state without error handling; failures stop the workflow.

💡 Hint

Think about how to isolate failures in parallel branches.

Using Parallel states with Catch blocks on each branch allows the workflow to handle failures locally and continue processing other branches, collecting results.