The correct answer involves implementing a connection pool sidecar container like PgBouncer in each EKS pod, alongside RDS Proxy and configuring the database with appropriate max_connections and Auto Scaling. This three-pronged approach efficiently manages database connections for microservices on Amazon EKS by reducing the total number of open connections to the relational database, preventing connection exhaustion during sudden spikes. RDS Proxy acts as a server-side connection broker, while the sidecar provides application-level pooling, and Auto Scaling ensures the database can scale horizontally to handle increased load. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your understanding of how to decouple microservices from direct database connections, with a common trap being to choose ElastiCache (which is for caching, not connection management) or direct connections (which increase load). Memory tip: think "Proxy + Pooler + Scaling" as the three pillars of resilient database connection management in Kubernetes environments.
DOP-C02 Resilient Cloud Solutions Practice Question
This DOP-C02 practice question tests your understanding of resilient cloud solutions. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 Amazon EKS. The application uses a relational database. The team wants to ensure that database connections are managed efficiently and that the database can withstand a sudden spike in connections from multiple microservices. Which solution should the DevOps engineer implement? (Choose THREE.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Deploy Amazon RDS Proxy in front of the database.
Option A is correct because RDS Proxy pools and shares database connections, reducing the number of connections to the database. Option D is correct because configuring the database with appropriate max_connections and using Auto Scaling (e.g., Aurora Auto Scaling) helps handle spikes. Option E is correct because using a connection pool sidecar (e.g., PgBouncer) in the EKS pods adds connection pooling at the application level. Option B (direct connections) would increase load. Option C (ElastiCache) is for caching, not connection management.
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.
✗
Use direct database connections from each microservice pod.
Why it's wrong here
Direct connections increase connection count and can overwhelm the database.
✗
Use Amazon ElastiCache for Redis to cache database query results.
Why it's wrong here
Caching reduces read load but does not manage connections.
✓
Deploy Amazon RDS Proxy in front of the database.
Why this is correct
RDS Proxy manages connection pooling and reduces database load.
Related concept
Read the scenario before looking for a memorised answer.
✓
Configure the database to have a higher max_connections and enable Auto Scaling.
Why this is correct
Higher connection limit and Auto Scaling help the database handle spikes.
Related concept
Read the scenario before looking for a memorised answer.
✓
Implement a connection pool sidecar container (e.g., PgBouncer) in each EKS pod.
Why this is correct
Sidecar connection poolers manage connections locally, reducing the number of open connections to the database.
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: Deploy Amazon RDS Proxy in front of the database. — Option A is correct because RDS Proxy pools and shares database connections, reducing the number of connections to the database. Option D is correct because configuring the database with appropriate max_connections and using Auto Scaling (e.g., Aurora Auto Scaling) helps handle spikes. Option E is correct because using a connection pool sidecar (e.g., PgBouncer) in the EKS pods adds connection pooling at the application level. Option B (direct connections) would increase load. Option C (ElastiCache) is for caching, not connection management.
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.