Decoupled Video Transcoding with Lambda and SQS
A media company is designing a video transcoding pipeline using AWS Lambda and Amazon S3. The pipeline must process videos uploaded to an S3 bucket, transcode them into multiple formats, and store the results in another S3 bucket. The processing time for each video can vary from a few seconds to several minutes. Which architecture will minimize cost and ensure all videos are processed, even if Lambda execution timeout is reached?
Quick Answer
The correct choice is to configure S3 event notifications to send messages to an SQS queue, with Lambda polling the queue and the SQS visibility timeout set to match the expected maximum processing time. This decoupled video transcoding pipeline with Lambda and SQS handles timeouts because if a Lambda invocation reaches its execution timeout, the message is not deleted from the queue; after the visibility timeout expires, the message reappears for another processing attempt, ensuring all videos are eventually transcoded. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of decoupling patterns and the trade-offs between synchronous and asynchronous processing—a common trap is choosing direct S3-to-Lambda invocation, which can lead to throttling and lost messages on timeout. Remember the key insight: SQS visibility timeout acts as a built-in retry mechanism for Lambda timeouts, making it the cost-effective, resilient choice without needing Step Functions or Kinesis. Memory tip: “Visibility timeout = Lambda’s second chance.”
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 S3 event notifications to send messages to an Amazon SQS queue. Have Lambda poll the queue and process each message. Set the SQS visibility timeout to match the expected maximum processing time.
Using S3 event notifications to send messages to an Amazon SQS queue decouples the upload from processing, allowing Lambda to poll the queue at its own pace. Setting the visibility timeout to match the expected maximum processing time ensures that if a Lambda invocation times out, the message becomes visible again after the visibility timeout, so it can be reprocessed. This minimizes cost (no additional services like Step Functions or Kinesis) and guarantees all videos are processed. Option A is incorrect because direct Lambda invocation via S3 events can lead to throttling under high concurrency, and the dead-letter queue only captures events after all retries fail, but timeouts within the function may not be handled elegantly. Option B is incorrect because AWS Step Functions adds cost and complexity for orchestration; while it can manage long-running workflows, the simpler SQS approach is more cost-effective. Option D is incorrect because Amazon Kinesis Data Streams is designed for real-time streaming and is overkill for this batch-oriented transcoding pipeline, increasing cost and complexity.
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 S3 event notifications to invoke Lambda directly and use a dead-letter queue to capture failed events.
Why it's wrong here
Direct invocation can cause throttling if many files are uploaded simultaneously; DLQ captures failures but does not handle timeout gracefully.
- ✗
Use AWS Step Functions to orchestrate the transcoding workflow, with each step as a separate Lambda function.
Why it's wrong here
Step Functions adds orchestration but does not inherently handle Lambda timeouts; it can add retry logic but increases cost and complexity.
- ✓
Configure S3 event notifications to send messages to an Amazon SQS queue. Have Lambda poll the queue and process each message. Set the SQS visibility timeout to match the expected maximum processing time.
Why this is correct
SQS decouples the trigger from processing, allowing Lambda to poll at its own pace; visibility timeout ensures messages are reprocessed if Lambda times out or fails.
- ✗
Use Amazon Kinesis Data Streams to ingest S3 events and have Lambda process records from the stream.
Why it's wrong here
Kinesis is designed for streaming data, not for event-driven file processing; it introduces additional cost and complexity.
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
This SAP-C02 question is part of Courseiva's 1,660-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SAP-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A media company is designing a new video processing pipeline on AWS. Videos are uploaded to an S3 bucket, which triggers an AWS Lambda function to start an AWS Elemental MediaConvert job. The MediaConvert job uses a custom job template. The pipeline must handle bursty uploads of up to 50 videos simultaneously. The company has noticed that some uploads are not being processed. The Lambda function is configured with a reserved concurrency of 10. The S3 event notification is configured to send events to the Lambda function. The MediaConvert job template is configured correctly. What is the most likely reason for the missed processing?
hard- A.The MediaConvert job template is not being applied correctly.
- B.The S3 event notification is not guaranteed to deliver events.
- ✓ C.The Lambda function's reserved concurrency of 10 is too low, causing throttling and missed events.
- D.The Lambda function is failing due to a timeout.
Why C: With reserved concurrency set to 10, only 10 Lambda invocations can happen concurrently; if more than 50 uploads occur simultaneously (burst), many events will be throttled and not processed. Option A is incorrect because the job template is configured correctly. Option B is incorrect because S3 event notifications are reliable for Lambda triggers. Option D is incorrect because there is no evidence of timeout issues.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.