- A
Increase reserved concurrency to 100
Correct: Increasing reserved concurrency allows more concurrent invocations, each processing up to 10 messages, thus increasing throughput without violating SQS batch size limits.
- B
Increase batch size to 100
Why wrong: Incorrect: The maximum batch size for SQS-triggered Lambda is 10, not 100, so this option is not feasible.
- C
Increase both batch size to 100 and reserved concurrency to a higher value
Why wrong: Incorrect: Batch size cannot be increased to 100 due to SQS limit; thus this option is invalid.
- D
Decrease batch size to 1 and increase reserved concurrency to 50
Why wrong: Incorrect: Decreasing batch size to 1 reduces the number of messages processed per invocation, reducing throughput even with increased concurrency.
DVA-C02 SQS batch size limit Practice Question
This DVA-C02 practice question tests your understanding of troubleshooting and optimization. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. A key principle to apply: sQS batch size limit. 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 developer is using AWS Lambda with a function that processes messages from an SQS queue. The function is configured with a batch size of 10 and reserved concurrency of 5. The queue has a large backlog, and messages are being throttled, leading to retries and eventual DLQ. The function is idempotent and can handle up to 100 messages per invocation. What is the most effective way to increase throughput without increasing throttling?
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 reserved concurrency to 100
Option A is correct because increasing reserved concurrency from 5 to 100 allows more concurrent Lambda invocations, each processing the maximum batch size of 10 messages from SQS. This directly increases throughput without attempting to exceed the SQS batch size limit of 10. Options B and C are invalid because the maximum batch size for SQS-triggered Lambda is 10, not 100. Option D reduces throughput by decreasing batch size.
Key principle: SQS batch size limit
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Increase reserved concurrency to 100
Why this is correct
Correct: Increasing reserved concurrency allows more concurrent invocations, each processing up to 10 messages, thus increasing throughput without violating SQS batch size limits.
Related concept
SQS batch size limit
- ✗
Increase batch size to 100
Why it's wrong here
Incorrect: The maximum batch size for SQS-triggered Lambda is 10, not 100, so this option is not feasible.
- ✗
Increase both batch size to 100 and reserved concurrency to a higher value
Why it's wrong here
Incorrect: Batch size cannot be increased to 100 due to SQS limit; thus this option is invalid.
- ✗
Decrease batch size to 1 and increase reserved concurrency to 50
Why it's wrong here
Incorrect: Decreasing batch size to 1 reduces the number of messages processed per invocation, reducing throughput even with increased concurrency.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap is that candidates may think increasing batch size is possible beyond 10, but AWS SQS Lambda integration caps the batch size at 10. They may also overlook that increasing reserved concurrency alone is sufficient to boost throughput while staying within the batch size limit.
Detailed technical explanation
How to think about this question
AWS Lambda integrates with SQS via event source mapping, which uses a long poll to retrieve messages from the queue. The batch size determines the maximum number of messages in a single event payload, and the reserved concurrency sets a per-function limit on concurrent executions. Under the hood, Lambda's SQS event source mapping uses a polling loop that respects the batch window and batch size; increasing both allows the function to consume messages faster without hitting the concurrency cap. In real-world scenarios, a common mistake is to only increase concurrency, which can lead to throttling at the account level (default 1000 concurrent executions) and increased costs due to more invocations, whereas increasing batch size reduces the number of invocations and improves cost efficiency.
KKey Concepts to Remember
- SQS batch size limit
- Reserved concurrency
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
SQS batch size limit
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
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 |
What to study next
Got this wrong? Here's your next step.
Review sQS batch size limit, then practise related DVA-C02 questions on the same topic to reinforce the concept.
- →
Troubleshooting and Optimization — study guide chapter
Learn the concepts, then practise the questions
- →
Troubleshooting and Optimization practice questions
Targeted practice on this topic area only
- →
All DVA-C02 questions
1,616 questions across all exam domains
- →
AWS Certified Developer Associate DVA-C02 study guide
Full concept coverage aligned to exam objectives
- →
DVA-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DVA-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Development with AWS Services practice questions
Practise DVA-C02 questions linked to Development with AWS Services.
Security practice questions
Practise DVA-C02 questions linked to Security.
Deployment practice questions
Practise DVA-C02 questions linked to Deployment.
Troubleshooting and Optimization practice questions
Practise DVA-C02 questions linked to Troubleshooting and Optimization.
DVA-C02 fundamentals practice questions
Practise DVA-C02 questions linked to DVA-C02 fundamentals.
DVA-C02 scenario practice questions
Practise DVA-C02 questions linked to DVA-C02 scenario.
DVA-C02 troubleshooting practice questions
Practise DVA-C02 questions linked to DVA-C02 troubleshooting.
Practice this exam
Start a free DVA-C02 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DVA-C02 question test?
Troubleshooting and Optimization — This question tests Troubleshooting and Optimization — SQS batch size limit.
What is the correct answer to this question?
The correct answer is: Increase reserved concurrency to 100 — Option A is correct because increasing reserved concurrency from 5 to 100 allows more concurrent Lambda invocations, each processing the maximum batch size of 10 messages from SQS. This directly increases throughput without attempting to exceed the SQS batch size limit of 10. Options B and C are invalid because the maximum batch size for SQS-triggered Lambda is 10, not 100. Option D reduces throughput by decreasing batch size.
What should I do if I get this DVA-C02 question wrong?
Review sQS batch size limit, then practise related DVA-C02 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
SQS batch size limit
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 →
Keep practising
More DVA-C02 practice questions
- A developer is troubleshooting an AWS Lambda function that is triggered by an S3 event. The function occasionally fails…
- A developer needs to call AWS APIs from application code running on EC2. Which credential source should the AWS SDK use…
- A developer needs to allow an IAM user in a different AWS account to assume a role in the developer's account. The role…
- A developer needs to grant an IAM role in Account B read-only access to objects in an S3 bucket in Account A. The bucket…
- An API Gateway HTTP API should allow access only to users authenticated by an external OIDC provider. Which authorizer t…
- A developer needs to allow an EC2 instance to read from a DynamoDB table. Which is the best practice to grant permission…
Last reviewed: Jun 11, 2026
This DVA-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 DVA-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.