DVA-C02 · Question #542
A developer is building an ecommerce application that uses multiple AWS Lambda functions. Each function performs a specific step in a customer order workflow, such as order processing and inventory ma
The correct answer is C. Configure an AWS Step Functions state machine to invoke the Lambda functions in a specific. AWS Step Functions provides native workflow orchestration for Lambda functions with built-in sequencing, error handling, and retry logic, requiring minimal operational setup.
Question
A developer is building an ecommerce application that uses multiple AWS Lambda functions. Each function performs a specific step in a customer order workflow, such as order processing and inventory management. The developer must ensure that the Lambda functions run in a specific order. Which solution will meet this requirement with the LEAST operational overhead?
Options
- AConfigure an Amazon Simple Queue Service (Amazon SQS) queue to contain messages about
- BConfigure an Amazon Simple Notification Service (Amazon SNS) topic to contain notifications
- CConfigure an AWS Step Functions state machine to invoke the Lambda functions in a specific
- DConfigure Amazon EventBridge Scheduler schedules to invoke the Lambda functions in a specific
How the community answered
(40 responses)- A8% (3)
- B3% (1)
- C80% (32)
- D10% (4)
Why each option
AWS Step Functions provides native workflow orchestration for Lambda functions with built-in sequencing, error handling, and retry logic, requiring minimal operational setup.
SQS queues decouple producers and consumers but do not enforce a specific execution order across multiple distinct Lambda functions in a workflow.
SNS is a pub/sub fanout service that broadcasts notifications to subscribers simultaneously; it does not sequence or orchestrate step-by-step Lambda invocations.
AWS Step Functions state machines are purpose-built for orchestrating multi-step workflows. They natively enforce execution order across Lambda functions using states, transitions, and built-in error handling without requiring custom coordination code or infrastructure management.
EventBridge Scheduler triggers functions on a time-based schedule, not in response to the completion of a prior step, making it unsuitable for sequential workflow orchestration.
Concept tested: Orchestrating sequential Lambda workflows with Step Functions
Source: https://docs.aws.amazon.com/step-functions/latest/dg/concepts-amazon-states-language.html
Community Discussion
No community discussion yet for this question.