Question 6 of 1,740
Resilient Cloud SolutionshardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to configure the SQS queue with a large visibility timeout, such as six hours, and use a redrive policy only after a high number of receives. This works because the visibility timeout makes a message invisible to consumers for its duration; by setting it long enough to cover the downstream service’s recovery window, you prevent the message from being repeatedly retried and prematurely sent to the dead-letter queue (DLQ). On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your understanding of how SQS visibility timeout directly prevents premature DLQ delivery by controlling retry timing rather than relying on immediate failure handling. A common trap is to assume that reducing the maxReceiveCount or using a shorter timeout will speed up recovery, but that actually forces messages into the DLQ faster. Instead, think of the visibility timeout as a “cool-down” period that gives the downstream service time to heal. Memory tip: “Long timeout, late DLQ” — the longer you make messages invisible, the more patience you give your system to recover.

DOP-C02 Resilient Cloud Solutions Practice Question

This DOP-C02 practice question tests your understanding of resilient cloud solutions. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 runs a critical application on AWS Lambda that processes messages from an Amazon SQS queue. The application must be resilient to downstream service failures. The team notices that when the downstream service is unhealthy, messages are repeatedly retried and eventually sent to the dead-letter queue (DLQ) before the service recovers. What design change would improve resilience by allowing automatic retries after the downstream service recovers?

Question 1hardmultiple choice
Full question →

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 the SQS queue with a large visibility timeout (e.g., 6 hours) and use a redrive policy only after a high number of receives. Keep the messages in the queue and retry when the downstream service becomes healthy.

Option A is correct because increasing the visibility timeout to a long duration (e.g., 6 hours) prevents messages from being repeatedly retried and sent to the DLQ while the downstream service is unhealthy. Instead, messages remain in the SQS queue and become visible again only after the visibility timeout expires, allowing automatic retries once the downstream service recovers. This approach avoids premature DLQ delivery and leverages SQS's built-in redrive policy based on maxReceiveCount.

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.

  • Configure the SQS queue with a large visibility timeout (e.g., 6 hours) and use a redrive policy only after a high number of receives. Keep the messages in the queue and retry when the downstream service becomes healthy.

    Why this is correct

    Long visibility timeout and high maxReceiveCount allow messages to be retried over an extended period.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Reduce the maxReceiveCount to 1 so that messages are sent to DLQ immediately, then reprocess them from DLQ later.

    Why it's wrong here

    This would send messages to DLQ before the service recovers, requiring manual intervention.

  • Increase the message retention period to 14 days and use a DLQ with high retention.

    Why it's wrong here

    Messages still go to DLQ after maxReceiveCount and are not automatically retried.

  • Use Amazon SNS to fan out messages to multiple SQS queues, each with different retry policies.

    Why it's wrong here

    SNS does not add retry logic; it just distributes messages.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often think increasing the DLQ retention or reducing retries (maxReceiveCount) is the solution, but the real key is controlling the retry timing via the visibility timeout to allow the downstream service to recover before messages are exhausted.

Detailed technical explanation

How to think about this question

Under the hood, SQS uses a visibility timeout to hide a message from other consumers after it is received; if the consumer fails to delete the message within that timeout, it becomes visible again for another attempt. By setting a large visibility timeout (e.g., 6 hours), you effectively pause retries until the timeout expires, giving the downstream service time to recover. The redrive policy's maxReceiveCount is only checked after each receive attempt, so a high maxReceiveCount combined with a long visibility timeout ensures messages are not moved to the DLQ prematurely.

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.

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

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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related DOP-C02 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DOP-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 DOP-C02 question test?

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 the SQS queue with a large visibility timeout (e.g., 6 hours) and use a redrive policy only after a high number of receives. Keep the messages in the queue and retry when the downstream service becomes healthy. — Option A is correct because increasing the visibility timeout to a long duration (e.g., 6 hours) prevents messages from being repeatedly retried and sent to the DLQ while the downstream service is unhealthy. Instead, messages remain in the SQS queue and become visible again only after the visibility timeout expires, allowing automatic retries once the downstream service recovers. This approach avoids premature DLQ delivery and leverages SQS's built-in redrive policy based on maxReceiveCount.

What should I do if I get this DOP-C02 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More DOP-C02 practice questions

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

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.