SAA-C03 Design High-Performing Architectures Practice Question
A company runs a media-processing pipeline that ingests thousands of small files per minute into Amazon S3 and triggers AWS Lambda functions for each object. Processing each file takes 2-3 seconds, and the team is seeing throttling errors and duplicated processing under load. They want to decouple ingestion from processing, buffer bursty traffic, and avoid duplicate deliveries to Lambda. Which solution should a solutions architect recommend?
⚠ Common exam trap
The trap here is assuming that increasing Lambda concurrency or adding provisioned concurrency resolves throttling from bursty direct event sources, when the real fix is to insert a buffer such as Amazon SQS between the producer and the consumer.
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
✓
Configure an Amazon S3 event notification to send events to an Amazon SQS standard queue, then have Lambda poll the queue with a batch size of 10 and a visibility timeout longer than the processing time.
Decoupling ingestion from processing with an SQS queue lets the pipeline absorb bursts while Lambda scales consumers based on backlog depth. A visibility timeout longer than the function execution time ensures that a message is not redelivered before processing completes, which prevents duplicates. Direct invocation from S3 does not provide buffering, and concurrency or acceleration features do not solve throttling or duplicate delivery.
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 an Amazon S3 event notification to send events to an Amazon SQS standard queue, then have Lambda poll the queue with a batch size of 10 and a visibility timeout longer than the processing time.
Why this is correct
S3 event notifications to SQS decouple ingestion from processing, and Lambda polling the queue scales with the backlog. A standard queue provides high throughput; setting the visibility timeout longer than the function runtime prevents duplicate processing because the message stays invisible until the function completes. This design absorbs bursts and avoids Lambda throttling caused by direct invocation.
- ✗
Increase the Lambda reserved concurrency to the maximum account limit and keep the direct S3 event notification to Lambda, so functions run in parallel and finish faster.
Why it's wrong here
Raising reserved concurrency increases parallel invocations but does not buffer traffic; S3 still delivers events synchronously and can produce at-least-once duplicates. It also consumes account concurrency, potentially starving other functions. Without a queue, throttling and duplicate deliveries remain, and the pipeline cannot absorb bursts gracefully.
- ✗
Use an S3 event notification to invoke an AWS Step Functions state machine that processes each file and retries on failure, with a Map state for parallelism.
Why it's wrong here
Step Functions is powerful for orchestration but adds per-transition cost and latency, and it does not natively buffer high-volume S3 events at thousands per minute without concurrency limits. It also does not address duplicate S3 event delivery inherently. The queue-based approach is simpler and more cost-effective for this decoupling pattern.
- ✗
Enable S3 Transfer Acceleration on the bucket and configure Lambda provisioned concurrency to handle the burst of events without cold starts.
Why it's wrong here
Transfer Acceleration speeds up uploads over long distances, not the event processing pipeline. Provisioned concurrency reduces cold starts but does not prevent Lambda throttling from too many concurrent direct invocations or stop duplicate S3 event deliveries. Neither feature buffers events or decouples ingestion from processing.
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
Courseiva writes every SAA-C03 question from scratch — 935 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
This SAA-C03 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 SAA-C03 exam.