The correct solution is to configure a dead-letter queue for unprocessed messages and implement Auto Scaling based on SQS queue depth. A dead-letter queue acts as a safety net, capturing messages that repeatedly fail processing after exhausting their retry count, thereby preventing permanent message loss. Meanwhile, Auto Scaling based on queue depth dynamically adjusts the number of application-tier EC2 instances in response to the backlog, ensuring the processing capacity scales with traffic spikes. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your understanding of decoupling patterns and resilience design—specifically how SQS dead-letter queues and Auto Scaling work together to handle burst traffic without data loss. A common trap is to assume that increasing the visibility timeout or switching to FIFO queues solves the problem, but neither addresses the core issue of insufficient processing capacity. Memory tip: think “DLQ catches the drops, scaling catches the wave”—the dead-letter queue catches failed messages, while queue-depth scaling catches the surge in demand.
DOP-C02 Resilient Cloud Solutions Practice Question
This DOP-C02 practice question tests your understanding of resilient cloud solutions. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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 company has deployed a multi-tier application on AWS. The web tier uses an Auto Scaling group of EC2 instances behind an Application Load Balancer. The application tier uses another Auto Scaling group of EC2 instances that process messages from an Amazon SQS queue. The database tier uses Amazon RDS Multi-AZ. Recently, the application experienced a complete outage when the SQS queue became overwhelmed with messages due to a sudden spike in traffic. The application tier could not process messages fast enough, causing the queue to grow indefinitely and eventually exceed the visibility timeout, leading to message loss and degraded performance. The DevOps engineer needs to improve the resilience of the architecture to handle traffic spikes without losing messages. Which solution should be implemented?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure a dead-letter queue for unprocessed messages and implement Auto Scaling based on SQS queue depth
Option C is correct because a dead-letter queue captures messages that cannot be processed after a number of attempts, preventing loss. Combined with Auto Scaling based on queue depth, it ensures the application tier scales to handle spikes. Option A is wrong because increasing visibility timeout only delays re-processing, it does not prevent message loss. Option B is wrong because limiting queue size causes rejection of messages. Option D is wrong because SQS FIFO does not improve resilience against spikes and may reduce throughput.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Limit the maximum message size and set a queue size limit to prevent overflow
Why it's wrong here
Rejects messages, causing loss.
✗
Replace the standard SQS queue with a FIFO SQS queue to ensure exactly-once processing
Why it's wrong here
FIFO does not solve scaling or message loss due to processing failures.
✗
Increase the visibility timeout in the SQS queue to allow more time for processing
Why it's wrong here
Does not prevent message loss if processing fails.
✓
Configure a dead-letter queue for unprocessed messages and implement Auto Scaling based on SQS queue depth
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Identify which DOP-C02 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Resilient Cloud Solutions — This question tests Resilient Cloud Solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure a dead-letter queue for unprocessed messages and implement Auto Scaling based on SQS queue depth — Option C is correct because a dead-letter queue captures messages that cannot be processed after a number of attempts, preventing loss. Combined with Auto Scaling based on queue depth, it ensures the application tier scales to handle spikes. Option A is wrong because increasing visibility timeout only delays re-processing, it does not prevent message loss. Option B is wrong because limiting queue size causes rejection of messages. Option D is wrong because SQS FIFO does not improve resilience against spikes and may reduce throughput.
What should I do if I get this DOP-C02 question wrong?
Identify which DOP-C02 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
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.
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.
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.