Question 1,541 of 1,660
SAP-C02 Continuous Improvement for Existing Solutions Practice Question
A company has a serverless application using AWS Lambda functions that process messages from an Amazon SQS queue. The queue receives a burst of messages daily. The Lambda function sometimes times out, causing messages to return to the queue and be reprocessed. How can the company improve the application to handle the burst without reprocessing failures?
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's reserved concurrency and timeout.
Increasing the reserved concurrency ensures Lambda can scale to handle the burst, and increasing the timeout allows the function to complete processing without timing out. Option A is wrong because reducing the batch size may reduce the number of messages processed per invocation but does not address the timeout issue. Option C is wrong because increasing the SQS visibility timeout would cause messages to be delayed before becoming visible again after a timeout, but it does not solve the root cause of the Lambda function timing out; it just delays reprocessing. Option D is wrong because a dead-letter queue is used to capture messages that repeatedly fail processing after maximum retries, not to prevent reprocessing of timeout failures.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reduce the batch size in the Lambda event source mapping.
Why it's wrong here
Reducing the batch size does not address the timeout issue, as the Lambda function can still time out on individual messages.
- ✓
Increase the Lambda function's reserved concurrency and timeout.
Why this is correct
Increasing reserved concurrency allows Lambda to scale to handle the burst, and increasing the timeout prevents timeouts during processing, thus reducing reprocessing.
- ✗
Increase the SQS visibility timeout to 6 minutes.
Why it's wrong here
Increasing the SQS visibility timeout does not prevent the Lambda function from timing out; it merely extends the time the message is invisible, but if the function times out, the message becomes visible again and is reprocessed.
- ✗
Configure a dead-letter queue for the SQS queue.
Why it's wrong here
Configuring a dead-letter queue does not prevent reprocessing; it only captures messages that have failed after a maximum number of retries, which does not address the timeout issue.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
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 →
Last reviewed: Jun 20, 2026
This SAP-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 SAP-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.