The correct answer is the circuit breaker pattern to stop calls to a failing service, along with retry with exponential backoff and the bulkhead pattern. The circuit breaker prevents cascading failures by halting requests to an unhealthy service, giving it time to recover, while retry with exponential backoff handles transient failures like throttling from DynamoDB or Lambda by introducing increasing delays with jitter, as seen in AWS SDK defaults. The bulkhead pattern isolates resources into separate pools so a failure in one service doesn’t exhaust shared threads or connections. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this question tests your ability to apply resilience patterns within a microservices architecture, often with a trap where candidates confuse retry logic with circuit breaking—remember that retry handles temporary glitches, but a circuit breaker stops repeated calls to a truly failing service. A useful memory tip is “C-B-R”: Circuit breaker, Bulkhead, Retry—think of a ship’s compartments staying afloat even if one leaks.
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 is migrating a monolithic application to a microservices architecture on AWS. To improve resilience, which THREE design patterns should be implemented? (Select THREE.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Retry with exponential backoff for transient failures
Option C is correct because implementing retry with exponential backoff allows services to handle transient failures (e.g., network timeouts, throttling) by automatically retrying operations after increasing delays, reducing load on recovering systems. This pattern is essential for microservices on AWS, where services like DynamoDB or Lambda may throttle requests, and exponential backoff (e.g., using jitter as per AWS SDK defaults) prevents cascading failures.
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.
✗
Synchronous communication between services to ensure consistency
Why it's wrong here
Synchronous calls increase coupling.
✗
Single shared database to maintain data consistency
Why it's wrong here
Creates a single point of failure and bottleneck.
✓
Retry with exponential backoff for transient failures
Why this is correct
Handles transient errors gracefully.
Related concept
Read the scenario before looking for a memorised answer.
✓
Bulkhead pattern to isolate critical services from non-critical ones
Read the scenario before looking for a memorised answer.
✓
Circuit breaker pattern to stop calls to a failing service
Why this is correct
Prevents cascading failures.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse synchronous communication (Option A) with resilience, but in microservices, synchronous calls increase failure propagation, while asynchronous patterns and the three selected patterns (retry, circuit breaker, bulkhead) are the correct resilience mechanisms.
Detailed technical explanation
How to think about this question
The retry with exponential backoff pattern often uses a base delay (e.g., 50 ms) multiplied by 2^n, with added jitter to avoid thundering herd problems; AWS SDKs implement this by default for services like DynamoDB (up to 3 retries). The circuit breaker pattern, when implemented with a library like Hystrix or resilience4j, monitors failure thresholds (e.g., 50% failures in a 10-second window) and trips to open state, preventing calls to a failing service and allowing it to recover. The bulkhead pattern isolates resources (e.g., thread pools) per service or client, ensuring that a failure in one critical service (e.g., payment) does not exhaust resources for another (e.g., catalog), often using separate connection pools or ECS task limits.
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 healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
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.
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: Retry with exponential backoff for transient failures — Option C is correct because implementing retry with exponential backoff allows services to handle transient failures (e.g., network timeouts, throttling) by automatically retrying operations after increasing delays, reducing load on recovering systems. This pattern is essential for microservices on AWS, where services like DynamoDB or Lambda may throttle requests, and exponential backoff (e.g., using jitter as per AWS SDK defaults) prevents cascading failures.
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 →
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.