DOP-C02 Question #299: Real Exam Question with Answer & Explanation

Question

A company is building a serverless application that uses AWS Lambda functions to process data. A BeginResponse Lambda function initializes data in response to specific application events. The company needs to ensure that a large number of Lambda functions are invoked after the BeginResponse Lambda function runs. Each Lambda function must be invoked in parallel and depends on only the outputs of the BeginResponse Lambda function. Each Lambda function has retry logic for invocation and must be able to fine-tune concurrency without losing data. Which solution will meet these requirements with the MOST operational efficiency?

Options

• ACreate an Amazon Simple Notification Service (Amazon SNS) topic. Modify the BeginResponse
• BCreate an Amazon Simple Queue Service (Amazon SQS) queue for each Lambda function that
• CCreate an Amazon Simple Queue Service (Amazon SQS) queue for each Lambda function that
• DCreate an AWS Step Functions Standard Workflow. Configure states in the workflow to invoke

Explanation

Using Amazon SQS ensures that each Lambda function has its own queue, allowing for parallel processing. Since each function has its own queue, the solution provides fine-tuned concurrency control, which can be adjusted based on the specific Lambda's requirements without affecting other functions. Each Lambda function can consume messages from its queue at its own rate and retry logic is handled with SQS visibility timeouts. Amazon SNS is used to fan out the message to all SQS queues. The BeginResponse function publishes a message to the SNS topic, and the SNS topic delivers that message to all the subscribed SQS queues. This ensures that all downstream Lambda functions are triggered in parallel after BeginResponse completes. By leveraging SQS, you can buffer requests to the Lambda functions, which ensures that no data is lost even if a downstream Lambda function is busy or experiencing issues. SQS also provides built-in retry capabilities, ensuring that messages are processed even in the case of transient This architecture is highly efficient and scalable. Each Lambda function can process events independently, and using SQS for concurrency control allows for flexible scaling. SQS and SNS work together seamlessly to handle large-scale, parallel invocations with reliability and fault

No community discussion yet for this question.