Step Functions

Question 1

How one can identify a Step Function’s single unit of work performed by a state machine?

Answer 1

Type must be “task” and Reource is a required parameter

"HelloWorld": {
  "Type": "Task",
  "Resource": "arn:aws:lambda:us-east-1:123456789012:function:HelloFunction",
  "Next": "AfterHelloWorldState",
  "Comment": "Run the HelloWorld Lambda function"
}

Question 2

The default Type for Step Functions state machines is:

Answer 2

Standard

Question 3

Step Functions Standard Workflows are ideal for:

Answer 3

long-running (up to one year), durable, and auditable workflows.

Question 4

In Step Functions Standard Workflows, for how long you can retrieve the full execution history?

Answer 4

You can retrieve the full execution history using the Step Functions API for up to 90 days after your execution completes.

Question 5

How Step Functions Standard Workflow executions are billed?

Answer 5

Standard Workflow executions are billed according to the number of state transitions processed.

Question 6

Step Functions Express Workflows are ideal for:

Answer 6

Express Workflows are ideal for:
- high-volume,
- event-processing workloads such as IoT data ingestion,
- streaming data processing and transformation
- mobile application backends.

Question 7

What are the Step functions Standard vs Express Workflows maximum durations?

Answer 7

One year on Standard and five minutes on Express.

Question 8

What are the Step functions Standard vs Express Workflows supported execution start rates?

Answer 8

• Standard: Over 2,000 per second
• Express: Over 100,000 per second

Question 9

What service can automate and orchestrate a multi-source high-volume flow of data in a scalable data management solution built using AWS services?

Answer 9

Step Functions