DOP-C02 Resilient Cloud Solutions Practice Question
A company uses AWS Lambda functions to process events from Amazon SQS. The Lambda function sometimes fails due to timeouts. The team wants to preserve the event for reprocessing. How should they configure the integration?
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
✓
Set up a DLQ on the SQS queue that receives the events
By configuring a dead-letter queue (DLQ) on the SQS queue, failed messages are preserved for later reprocessing.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Set up a DLQ on the SQS queue that receives the events
Why this is correct
Configuring a dead-letter queue on the SQS queue ensures that any messages that are not successfully processed by the Lambda function are redirected to the DLQ for later analysis and reprocessing. This directly addresses the need to preserve failed events.
- ✗
Use Lambda reserved concurrency
Why it's wrong here
Reserved concurrency allocates a guaranteed ceiling of concurrent executions for the Lambda function, protecting performance by preventing other functions from exhausting account-level concurrency and reducing throttling of the SQS event source mapping. However, it does not capture or preserve individual events that still fail processing; when an invocation errors, SQS relies on the queue's visibility timeout and redrive policy to handle retry and eventual quarantine. Without a queue-level DLQ, failed messages simply remain in the source queue or are discarded after retries, so reserved concurrency alone offers no reprocessing or analysis mechanism.
- ✗
Enable Lambda function DLQ with SNS topic
Why it's wrong here
Enabling a DLQ on the Lambda function (with an SNS topic) is only applicable for asynchronous invocations, not for event source mappings like SQS. For SQS-triggered Lambda, the proper DLQ is configured on the SQS queue itself.
- ✗
Increase Lambda timeout to maximum
Why it's wrong here
Raising the Lambda timeout to the 15-minute maximum gives the function more wall-clock time to finish processing, which may avoid termination of slow but otherwise valid executions. But it does not create a separate destination for events that fail, and if the failure stems from a malformed payload or an external dependency outage, a longer timeout will only delay the eventual error. In fact, longer timeouts increase the required visibility timeout on SQS, which can defer retries and slow down the overall pipeline, while still relying on the queue's redrive policy to move failed messages to a DLQ.
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 |
Go deeper
Related to this question
About these practice questions
Courseiva writes every DOP-C02 question from scratch — 1,298 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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DOP-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 DOP-C02 exam.