Which combination of steps will meet this requirement with the LEAST implementation effort?
(Choose two.)
Update the existing Lambda function’s code to send an Amazon CloudWatch custom metric for the number of orders in a batch for each partner.
Create a new Lambda function as an Amazon Kinesis data stream consumer. Configure the new Lambda function to track orders and to publish to the SNS topic when a batch contains no orders.
Set up an Amazon CloudWatch alarm that will send a notification to the SNS topic when the value of the custom metric is 0.
Schedule a new Lambda function to analyze Amazon CloudWatch metrics every 24 hours to identify batches that contain no orders. Configure the Lambda function to publish to the SNS topic.
Modify the existing Lambda function to log orders to an Amazon Kinesis data stream.
Explanations:
Updating the existing Lambda function to send a custom metric to CloudWatch is efficient and requires minimal implementation effort. This allows tracking the number of orders in a batch and serves as a foundation for triggering alerts based on batch size.
Creating a new Lambda function as an Amazon Kinesis data stream consumer would require additional setup and complexity, which is unnecessary. The task can be accomplished without a new data stream or Lambda function.
Setting up a CloudWatch alarm to monitor the custom metric and trigger a notification to the SNS topic when the value is 0 meets the requirement directly. It is simple, leverages CloudWatch, and has minimal implementation overhead.
Scheduling a new Lambda function to analyze metrics every 24 hours introduces unnecessary delay and complexity. The requirement is to publish to the SNS topic “as soon as possible,” which this solution does not satisfy.
Modifying the Lambda function to log orders to a Kinesis data stream would add unnecessary complexity by introducing Kinesis when it’s not required for this task. The solution can be achieved more simply without using Kinesis.