The answer is to ensure the Lambda function writes logs to stdout or stderr, as CloudWatch Logs will automatically capture them. This is correct because the AWS Lambda runtime natively streams all output from stdout (e.g., `print` or `console.log`) and stderr directly to CloudWatch Logs, regardless of whether the function succeeds or fails—even during a memory exhaustion event. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this question tests your understanding of Lambda’s built-in logging behavior versus the common trap of assuming you need a custom agent or a dead-letter queue to capture failure logs. The key insight is that Lambda logs are always shipped to CloudWatch Logs by default; a failure does not prevent this, as the runtime captures output up to the point of termination. Memory tip: think of stdout/stderr as the “always-on” pipeline—no matter how the function ends, what it wrote to these streams is already sent.
DOP-C02 Monitoring and Logging Practice Question
This DOP-C02 practice question tests your understanding of monitoring and logging. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A DevOps engineer is configuring CloudWatch Logs for a Lambda function that processes streaming data from Kinesis. The function sometimes fails due to memory exhaustion. The engineer wants to ensure that logs from the function are shipped to CloudWatch Logs even when the function fails. Which configuration should be used?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Ensure the Lambda function writes logs to stdout or stderr; CloudWatch Logs will automatically capture them
Lambda functions automatically send all output written to stdout (via print or console.log) and stderr to CloudWatch Logs, regardless of whether the function succeeds or fails. This is a built-in behavior of the Lambda runtime, so no additional agents or configuration are needed to capture logs from a failed invocation due to memory exhaustion.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Configure a Kinesis Agent on the Lambda execution environment to stream logs to CloudWatch Logs
Why it's wrong here
Incorrect. Lambda does not have a Kinesis Agent; logs are sent via the Lambda runtime.
✗
Install the CloudWatch Logs agent on the Lambda function to continuously send logs
Why it's wrong here
Incorrect. Lambda functions are stateless; you cannot install agents.
✗
Enable detailed CloudWatch metrics for the Lambda function
Why it's wrong here
Incorrect. Detailed metrics do not capture logs.
✓
Ensure the Lambda function writes logs to stdout or stderr; CloudWatch Logs will automatically capture them
Why this is correct
Correct. Lambda automatically captures stdout/stderr and sends to CloudWatch Logs regardless of function success or failure.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may overthink the solution and assume a separate agent or service is required for log shipping in failure scenarios, when in fact Lambda’s native stdout/stderr capture works automatically and reliably even on invocation failure.
Detailed technical explanation
How to think about this question
Under the hood, the Lambda runtime wraps the function handler and captures all stdout/stderr output, forwarding it to the CloudWatch Logs service via the AWS Logs API. This happens asynchronously and is independent of the function’s exit code or error state, so even if the function crashes due to memory exhaustion (OutOfMemoryError), the logs written before the crash are still delivered. The Lambda execution environment does not persist any state or allow custom agents, making stdout/stderr the only reliable mechanism for log shipping.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Monitoring and Logging — This question tests Monitoring and Logging — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Ensure the Lambda function writes logs to stdout or stderr; CloudWatch Logs will automatically capture them — Lambda functions automatically send all output written to stdout (via print or console.log) and stderr to CloudWatch Logs, regardless of whether the function succeeds or fails. This is a built-in behavior of the Lambda runtime, so no additional agents or configuration are needed to capture logs from a failed invocation due to memory exhaustion.
What should I do if I get this DOP-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This DOP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DOP-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.