The correct choice is to configure the application’s connection string to use the RDS read-replica endpoint with a retry mechanism. This works because the read-replica endpoint is a static DNS name that remains constant during a Multi-AZ failover, eliminating the 60-second DNS propagation delay that caused the original downtime. By pointing the application directly to this endpoint, connections can be re-established as soon as the replica promotes to primary, and a retry mechanism handles transient failures during the brief promotion window. On the AWS Certified SAP on AWS Specialty PAS-C01 exam, this scenario tests your understanding of how to architect for high availability beyond basic Multi-AZ, often trapping candidates who assume DNS TTL reduction alone solves the problem. Remember: the read-replica endpoint bypasses DNS entirely, so your application doesn’t wait for a record update. Memory tip: “Static endpoint, instant reconnect—no DNS wait, no downtime defect.”
PAS-C01 Operations and Maintenance Practice Question
This PAS-C01 practice question tests your understanding of operations and maintenance. 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 runs a critical workload on Amazon RDS for PostgreSQL with Multi-AZ. The operations team notices that during a recent failover test, the DNS record updated in about 60 seconds. However, the application experienced a 2-minute downtime because some connections were not re-established quickly. What should the team do to reduce downtime during failover?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the application's connection string to use the RDS read-replica endpoint with a retry mechanism.
Option C is correct because configuring the application's connection string to use the RDS read-replica endpoint with a retry mechanism allows the application to quickly fail over to the read replica during a Multi-AZ failover. The read-replica endpoint remains constant and does not rely on DNS propagation, reducing downtime from DNS TTL delays. Combined with a retry mechanism, this ensures connections are re-established immediately after the failover completes, rather than waiting for the DNS record to update.
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.
✗
Enable automated backups with a short retention period.
Why it's wrong here
Backups are unrelated to failover connection handling.
✗
Increase the TTL of the RDS DNS record to 300 seconds.
Why it's wrong here
Higher TTL means clients cache old IP longer, increasing downtime.
✓
Configure the application's connection string to use the RDS read-replica endpoint with a retry mechanism.
Why this is correct
Using the read replica endpoint can redirect traffic faster; retries help re-establish connections.
Related concept
Read the scenario before looking for a memorised answer.
✗
Place a Network Load Balancer in front of the RDS instance.
Why it's wrong here
NLB does not support RDS directly; adds unnecessary complexity.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think increasing DNS TTL speeds up failover, but in reality, a higher TTL increases client-side caching delay, making downtime worse, while the correct approach is to use a static endpoint (like the read-replica endpoint) with retry logic to bypass DNS propagation issues entirely.
Detailed technical explanation
How to think about this question
During a Multi-AZ failover, RDS updates the DNS record to point to the standby instance, but DNS caching at the client or resolver level can cause delays up to the TTL value (default 60 seconds). Using the read-replica endpoint (which is a CNAME pointing to the current primary) avoids this because the application reconnects to a static endpoint that is updated internally by RDS without relying on client-side DNS cache expiry. The retry mechanism is critical because the failover itself takes a few seconds, and the application must handle transient connection failures gracefully.
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.
Operations and Maintenance — This question tests Operations and Maintenance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure the application's connection string to use the RDS read-replica endpoint with a retry mechanism. — Option C is correct because configuring the application's connection string to use the RDS read-replica endpoint with a retry mechanism allows the application to quickly fail over to the read replica during a Multi-AZ failover. The read-replica endpoint remains constant and does not rely on DNS propagation, reducing downtime from DNS TTL delays. Combined with a retry mechanism, this ensures connections are re-established immediately after the failover completes, rather than waiting for the DNS record to update.
What should I do if I get this PAS-C01 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 PAS-C01 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 PAS-C01 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.