The answer is to use Amazon RDS Proxy to pool database connections, enable Aurora Auto Scaling with a higher maximum ACU, and implement exponential backoff with jitter in application retries. During rapid scaling in ECS Fargate, each new task creates multiple database connections, overwhelming Aurora Serverless v2 and causing ACU spikes to 100%. RDS Proxy reduces connection overhead by reusing a managed pool, while Aurora Auto Scaling dynamically adjusts ACUs to absorb bursts, and exponential backoff prevents a thundering herd of retries from compounding the load. On the DOP-C02 exam, this scenario tests your ability to decouple compute scaling from database scaling—a common trap is mistaking ElastiCache for write-heavy fixes or increasing task memory, which ignores the database bottleneck. Remember the mnemonic “PROXY, SCALE, BACKOFF” to recall the three pillars: Pool connections, Raise ACU limits, and Offset retry storms.
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 runs a containerized application on Amazon ECS with Fargate. The application uses an Application Load Balancer (ALB) and stores data in Amazon Aurora Serverless v2. The application experiences intermittent timeouts during periods of rapid scaling. The DevOps engineer notices that the Aurora database's ACU utilization spikes to 100% during these events. What should the engineer do to improve resilience? (Choose THREE.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement exponential backoff and jitter in application retry logic.
Option A is correct because enabling Aurora Auto Scaling with a higher maximum ACU allows the database to handle bursts. Option B is correct because using RDS Proxy reduces connection overhead and helps manage scaling. Option C is correct because implementing exponential backoff and jitter in application retries prevents thundering herd. Option D (increasing ECS task memory) does not address database bottleneck. Option E (using ElastiCache) could offload reads but not writes; the issue is write-heavy scaling.
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.
✗
Increase the Fargate task memory and CPU limits.
Why it's wrong here
The bottleneck is the database, not compute.
✓
Implement exponential backoff and jitter in application retry logic.
Why this is correct
Prevents overwhelming the database with retries during recovery.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add Amazon ElastiCache in front of the database for caching.
Why it's wrong here
Caching helps read-heavy workloads; the issue is write spikes.
✓
Configure Aurora Auto Scaling with a higher maximum ACU limit.
Why this is correct
Allows the database to scale up capacity during traffic spikes.
Related concept
Read the scenario before looking for a memorised answer.
✓
Use Amazon RDS Proxy to pool database connections.
Why this is correct
RDS Proxy reduces connection churn and latency, improving resilience under load.
Related concept
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 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 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: Implement exponential backoff and jitter in application retry logic. — Option A is correct because enabling Aurora Auto Scaling with a higher maximum ACU allows the database to handle bursts. Option B is correct because using RDS Proxy reduces connection overhead and helps manage scaling. Option C is correct because implementing exponential backoff and jitter in application retries prevents thundering herd. Option D (increasing ECS task memory) does not address database bottleneck. Option E (using ElastiCache) could offload reads but not writes; the issue is write-heavy scaling.
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.