DVA-C02 · Question #748
A developer uses AWS Step Functions to build a complex workflow. The workflow takes several hours to finish running. An AWS Lambda function runs as part of the end of the workflow. However, the Lambda
The correct answer is C. Redrive the Step Functions workflow from the failed Lambda function step.. The most operationally efficient way to troubleshoot Lambda function errors in a long-running Step Functions workflow is to redrive the workflow from the failed Lambda function step. This avoids rerunning the entire multi-hour workflow, saving time and compute resources while all
Question
A developer uses AWS Step Functions to build a complex workflow. The workflow takes several hours to finish running. An AWS Lambda function runs as part of the end of the workflow. However, the Lambda function is generating errors. The developer must troubleshoot the Lambda function errors. Which solution will meet this requirement in the MOST operationally efficient way?
Options
- ACreate a test event that contains the JSON that serves as the input to the Lambda function step.
- BEnable active tracing on the function Visualize the results in the Amazon CloudWatch service
- CRedrive the Step Functions workflow from the failed Lambda function step.
- DAdd a retrier to the Lambda function step of the workflow for the States.IntrinsicFailure error type.
How the community answered
(36 responses)- A11% (4)
- B6% (2)
- C64% (23)
- D19% (7)
Explanation
The most operationally efficient way to troubleshoot Lambda function errors in a long-running Step Functions workflow is to redrive the workflow from the failed Lambda function step. This avoids rerunning the entire multi-hour workflow, saving time and compute resources while allowing you to quickly isolate and debug the error in the Lambda step.
Community Discussion
No community discussion yet for this question.