SAP-C02 Continuous Improvement for Existing Solutions Practice Question
A company uses Amazon RDS for MySQL with Multi-AZ. The operations team notices that during a failover, the application experiences errors for about 2 minutes. The application uses a JDBC connection pool. Which solution should the team implement to reduce the failover impact?
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 JDBC connection string with a timeout and implement automatic retry logic.
Implementing a timeout and automatic retry logic in the JDBC connection pool ensures that after a failover, the application can quickly detect the failed connection and reconnect to the new primary. Option A is incorrect because restarting the application via CloudWatch Events and Lambda does not directly address connection failures and may cause additional downtime. Option B is incorrect: while Amazon RDS Proxy can help manage connections and reduce latency, it does not eliminate the need for application-level retry logic; during failover, connections are dropped and need to be re-established. Option D is incorrect because increasing the TTL of the RDS DNS record would actually cause the application to cache the old DNS record longer, delaying failover detection.
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 Amazon CloudWatch Events to trigger a Lambda function that restarts the application.
Why it's wrong here
Restarting the application is not necessary; retry is sufficient.
- ✗
Use Amazon RDS Proxy to manage database connections.
Why it's wrong here
RDS Proxy pools connections but still requires application retry logic.
- ✓
Configure the JDBC connection string with a timeout and implement automatic retry logic.
Why this is correct
Retry logic allows the application to reconnect after failover.
- ✗
Increase the TTL for the RDS DNS record to 60 seconds.
Why it's wrong here
TTL affects DNS caching, not connection timeout.
Visual reference
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
About these practice questions
This SAP-C02 question is part of Courseiva's 1,660-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-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 SAP-C02 exam.