How to search serverless logs with least operational overhead?

A developer builds a serverless application on AWS by using Amazon API Gateway, AWS Lambda functions, and Amazon Route 53. During testing, the developer notices errors but cannot immediately locate the root cause. To identify the errors, the developer needs to search all the application's logs. What should the developer do to meet these requirements with the LEAST operational overhead?

  1. Set up API Gateway health checks to monitor the application's availability. Use the Amazon CloudWatch PutMetricData API operation to publish the logs to CloudWatch. Search and query the logs by using Amazon Athena.
  2. Set up Route 53 health checks to monitor the application's availability. Turn on AWS CloudTrail logs for all the AWS services that the application uses. Send the logs to a specified Amazon S3 bucket. Use Amazon Athena to query the log files directly from Amazon S3.
  3. Configure all the application's AWS services to publish a real-time feed of log events to an Amazon Kinesis Data Firehose delivery stream. Configure the delivery stream to publish all the logs to an Amazon S3 bucket. Use Amazon OpenSearch Service to search and analyze the logs.
  4. Set up Route 53 health checks to monitor the application's availability. Turn on Amazon CloudWatch Logs for the API Gateway stages to log API requests with a JSON log format. Use CloudWatch Logs Insights to search and analyze the logs from the AWS services that the application uses. Source Reference Answer

Community Votes

D
100%

100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

This question tests the ability to select native AWS monitoring tools for log analysis, with the common trap being the selection of over-engineered solutions like Athena or OpenSearch Service that introduce unnecessary operational overhead.

For serverless applications requiring centralized log analysis with minimal setup, Amazon CloudWatch Logs and CloudWatch Logs Insights provide the most efficient native solution. The community consensus confirms that leveraging built-in AWS logging tools reduces operational overhead compared to third-party or complex data pipeline architectures.

Selecting Option C is a common mistake because Amazon OpenSearch Service offers powerful search capabilities, but configuring Kinesis Data Firehose and OpenSearch creates significant operational overhead compared to the native CloudWatch Logs Insights service.

Community Discussion (3 comments)

Mo_1981 👍 2 Selected: D
https://docs.aws.amazon.com/lambda/latest/dg/monitoring-cloudwatchlogs.html
albert_kuo 👍 3 Selected: D
Minimal Operational Overhead: Uses built-in AWS services with minimal configuration. Centralized Log Analysis: CloudWatch Logs Insights provides a powerful, interactive query interface to analyze logs. Cost-Efficient: Utilizing existing AWS services like CloudWatch and Route 53 reduces the need for additional third-party tools or infrastructure.
catoteja 👍 4 Selected: D
It's D-

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Option D is correct because it utilizes Amazon CloudWatch Logs, the native logging solution for AWS Lambda and API Gateway. CloudWatch Logs Insights provides a built-in, interactive query interface that allows developers to instantly search and analyze log data without managing infrastructure or configuring complex data pipelines, directly meeting the requirement for least operational overhead.

Why the Other Options Are Wrong

Option A incorrectly suggests using the PutMetricData API for logging (which is for metrics) and using Athena, which adds unnecessary complexity for simple log searching. Option B suggests using CloudTrail, which captures API call history for auditing rather than detailed application error logs, and querying S3 via Athena is less immediate than native tools. Option C involves setting up Kinesis Data Firehose and OpenSearch Service, which requires substantial provisioning and management, violating the low operational overhead constraint.

Community Comment Notes

Community feedback strongly supports Option D, emphasizing its minimal configuration needs and cost-efficiency. Users highlighted that CloudWatch Logs Insights offers a powerful query interface and that relying on existing AWS services like CloudWatch eliminates the need for third-party tools or extra infrastructure, making it the best choice for a serverless environment.

Official Reference

Exam Strategy

When you see 'least operational overhead' in the context of monitoring AWS services, prioritize native, integrated solutions like CloudWatch Logs and Insights over complex data pipelines. Avoid over-engineering with services like Kinesis or Athena unless the question specifically requires features not available in standard monitoring tools.

Related Analysis

A developer is publishing critical log data to a log group i

A-Grade

A developer is building an application integrating an Amazon

A-Grade

A company runs an application on AWS. The application uses a

A-Grade

Practice All DVA-C02 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DVA-C02 Practice Test →

← Back to DVA-C02 Study Guide