You have a task to build the AWS infrastructure resources for a project. In this project, there is a high-volume event source in an Amazon SQS queue. Certain steps are needed to process the messages. You want to implement a state machine and visualize the workflow. The AWS resources should be managed by a configuration orchestration tool so that they can be redeployed easily in another environment. Which tools should you use for this task?

Answer options:

A.Configure an Elastic Beanstalk worker environment for the SQS queue and include Step Functions in the environment to implement the state machine. 
B.Create a State Machine with Lambda tasks using AWS CloudFormation templates.
C.Configure an OpsWorks stack to automate the configurations of Step Functions that pull messages from the SQS queue and process messages in a state machine.
D.Configure an AWS CloudFormation stack to create the Step Functions using Lambda. Put each Lambda function in a separate Lambda layer.

Correct Answer – B
The State Machine with Lambda tasks for Step Functions can be implemented using CloudFormation. The reference can be found in https://docs.aws.amazon.com/step-functions/latest/dg/tutorial-lambda-state-machine-cloudformation.html.
Option A is incorrect: Because Elastic Beanstalk is not appropriate for Step Functions or Lambda functions. CloudFormation should be used as an infrastructure management tool.
Option B is CORRECT: Because CloudFormation can set up resources such as Lambda function (AWS::Lambda:: Function) and Step Functions state machine (AWS::StepFunctions:: StateMachine) in a single template. Therefore we create a state machine with some lambda tasks to visualize the workflow
Option C is incorrect: Similar to option A, OpsWorks is not a suitable tool for Step Functions. CloudFormation should be chosen.
Option D is incorrect: Because it is incorrect to put each Lambda function in a separate Lambda layer. This is not how Lambda layers work. Details please check https://docs.aws.amazon.com/lambda/latest/dg/configuration-layers.html.