Amazon
SOA-C02 · Question #133
A development team created and deployed a new AWS Lambda function 15 minutes ago. Although the function was invoked many times, Amazon CloudWatch Logs are not showing any log messages. What is one…
The correct answer is A. The developers did not enable log messages for this Lambda function. When the Lambda function's execution role doesn't have the necessary permissions to create log streams or log groups in CloudWatch Logs, the logs won't be generated or stored.
Submitted by paula_co· Mar 30, 2026Monitoring, Logging, and Remediation
Question
A development team created and deployed a new AWS Lambda function 15 minutes ago. Although the function was invoked many times, Amazon CloudWatch Logs are not showing any log messages. What is one cause of this?
Options
- AThe developers did not enable log messages for this Lambda function.
- BThe Lambda function's role does not include permissions to create CloudWatch Logs items.
- CThe Lambda function raises an exception before the first log statement has been reached.
- DThe Lambda functions creates local log files that have to be shipped to CloudWatch Logs first
How the community answered
(27 responses)- A85% (23)
- B4% (1)
- C7% (2)
- D4% (1)
Explanation
When the Lambda function's execution role doesn't have the necessary permissions to create log streams or log groups in CloudWatch Logs, the logs won't be generated or stored.
Topics
#Lambda#CloudWatch Logs#IAM permissions#logging
Community Discussion
No community discussion yet for this question.