DVA-C02 · Question #202
A developer is creating a machine learning (ML) pipeline in AWS Step Functions that contains AWS Lambda functions. The developer has configured an Amazon Simple Queue Service (Amazon SQS) queue to…
The correct answer is D. Use AWS Step Functions Local with mocked service integrations. AWS Step Functions Local with mocked service integrations (D) is the correct choice because it allows developers to run Step Functions workflows entirely on their local machine and substitute real AWS service calls (SQS, S3, Lambda, etc.) with mock responses - exactly what the…
Question
A developer is creating a machine learning (ML) pipeline in AWS Step Functions that contains AWS Lambda functions. The developer has configured an Amazon Simple Queue Service (Amazon SQS) queue to deliver ML model parameters to the ML pipeline to train ML models. The developer uploads the trained models are uploaded to an Amazon S3 bucket. The developer needs a solution that can locally test the ML pipeline without making service integration calls to Amazon SQS and Amazon S3. Which solution will meet these requirements?
Options
- AUse the Amazon CodeGuru Profiler to analyze the Lambda functions used in the AWS Step
- BUse the AWS Step Functions Local Docker Image to run and locally test the Lambda functions.
- CUse the AWS Serverless Application Model (AWS SAM) CLI to run and locally test the Lambda
- DUse AWS Step Functions Local with mocked service integrations.
How the community answered
(19 responses)- A5% (1)
- C11% (2)
- D84% (16)
Explanation
AWS Step Functions Local with mocked service integrations (D) is the correct choice because it allows developers to run Step Functions workflows entirely on their local machine and substitute real AWS service calls (SQS, S3, Lambda, etc.) with mock responses - exactly what the question requires.
- A is wrong because CodeGuru Profiler is a code performance/profiling tool, not a local testing framework; it doesn't mock service integrations or run pipelines locally.
- B is wrong because the Step Functions Local Docker Image enables local workflow execution, but it does not provide built-in mocked service integrations for SQS or S3 on its own.
- C is wrong because AWS SAM CLI is designed for testing serverless applications (Lambda-centric), not for orchestrating and mocking Step Functions state machine service integrations end-to-end.
Memory tip: Think "mock = D." Whenever a question mentions local testing + avoiding real AWS service calls in the context of Step Functions, the keyword "mocked service integrations" maps directly to Step Functions Local - it's the only tool in the AWS ecosystem purpose-built to intercept and simulate those integration calls during development.
Topics
Community Discussion
No community discussion yet for this question.