A company uses an AWS Lambda function to process user uploads to an Amazon S3 bucket. The Lambda function runs in response to Amazon S3 PutObject events. A SysOps administrator needs to set up…

Question

Options

• ACollect Amazon CloudWatch logs for the Lambda function. Create a metric filter to extract the
• BCollect Amazon CloudWatch metrics for the Lambda function to extract the function runtime.
• CConfigure an Amazon CloudWatch metric filter to capture the runtime of the Lambda function. Set
• DUse Amazon CloudWatch Logs Insights to query Lambda logs for the function runtime. Set up a

• A
  18% (3)
• B
  71% (12)
• C
  6% (1)
• D
  6% (1)

Explanation

AWS Lambda automatically publishes operational metrics to Amazon CloudWatch, including Duration, which represents the time a function invocation takes to run. To alert when processing time exceeds 10 seconds, the most direct and operationally efficient solution is to create a CloudWatch alarm on the Lambda Duration metric and configure the alarm action to publish to an SNS topic. This meets the monitoring requirement without requiring log parsing or additional query mechanisms. Option B fits best because it uses the built-in metric stream for Lambda observability: CloudWatch metrics are near real-time, require minimal configuration, and alarms are a standard CloudOps practice for proactive notification. The alarm can be configured with the appropriate statistic (for example, Maximum or p99 via metric math where applicable) and a threshold of 10,000 milliseconds, ensuring the operations team is notified before performance degrades

No community discussion yet for this question.