SOA-C02 Monitoring, Logging, and Remediation Practice Question
A company has an AWS Lambda function that processes files uploaded to an S3 bucket. The function fails intermittently with a timeout error. What should the SysOps administrator do to monitor and resolve this issue?
⚠ Common exam trap
A common mix-up: candidates confuse Lambda's scaling behavior with EC2 Auto Scaling, or assume that provisioned concurrency fixes execution duration issues, when in fact it only addresses cold start latency.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Increase the Lambda function timeout and review the function logs in CloudWatch Logs.
Increasing the Lambda function timeout directly addresses the intermittent timeout error by allowing the function more time to complete execution before Lambda terminates it. Reviewing CloudWatch Logs is essential to identify the root cause, such as slow downstream dependencies or inefficient code, enabling targeted optimization. This approach aligns with standard troubleshooting for Lambda timeout issues.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Place the S3 bucket in a different AWS region to reduce latency.
Why it's wrong here
Moving the S3 bucket to a different region does not resolve a Lambda timeout because the timeout is enforced on the function's total execution duration, not on network round-trip time. Even if latency to Amazon S3 is reduced, the function code may still take longer than the configured timeout to process the file. Additionally, changing regions could actually increase latency if the Lambda function remains in its original region, and it may introduce compliance or data sovereignty issues.
- ✗
Enable provisioned concurrency for the Lambda function.
Why it's wrong here
Provisioned concurrency pre-warms Lambda execution environments to reduce cold start latency, but it has no effect on the function's maximum execution time. The timeout is a hard limit on how long an invocation can run, and once that limit is reached, the execution is terminated regardless of how many concurrent environments are available. Therefore, this option incorrectly conflates performance latency with the fundamental execution duration constraint.
- ✓
Increase the Lambda function timeout and review the function logs in CloudWatch Logs.
Why this is correct
A Lambda timeout error indicates that the function exceeded its configured execution time limit, so increasing the timeout gives the process more time to complete its work. Reviewing CloudWatch Logs is essential to determine why the function is slow, such as inefficient logic, a large download, or a blocking call to another service. After increasing the timeout, verify both the function's memory allocation and the maximum allowed timeout (15 minutes) to ensure the new setting is valid, and monitor logs to confirm the root cause is resolved.
- ✗
Configure EC2 Auto Scaling to launch more instances for the Lambda function.
Why it's wrong here
EC2 Auto Scaling manages the horizontal scaling of Amazon EC2 instances based on policies, but Lambda functions do not run on EC2 instances that you manage or control. AWS Lambda is a serverless compute service where scaling is automatic and handled entirely by the service based on request rate. Launching additional EC2 instances would not affect Lambda's execution environment, so this option is not a valid remedy for a Lambda timeout.
Visual reference
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
One of 1,169 original SOA-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SOA-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 SOA-C02 exam.