The answer is a hardcoded IP address or an endpoint pointing to the old primary RDS instance instead of the RDS DNS name. This is correct because after a Multi-AZ failover, the standby is promoted to primary, but any application code that references the old primary’s IP or a static endpoint will fail to connect—the RDS DNS CNAME record is the only reliable way to automatically follow the new primary. On the AWS Certified Solutions Architect Professional SAP-C02 exam, this scenario tests your understanding of how RDS Multi-AZ failover application connectivity issues arise from DNS dependency, not from failover speed or security group misconfiguration. A common trap is assuming the failover itself is the bottleneck, when in fact the real culprit is application-side endpoint resolution. Memory tip: “DNS, not IP—let AWS handle the flip.”
SAP-C02 Continuous Improvement for Existing Solutions Practice Question
This SAP-C02 practice question tests your understanding of continuous improvement for existing 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 financial services company runs a critical application on Amazon EC2 instances in an Auto Scaling group across multiple Availability Zones. The application uses an Amazon RDS for MySQL database with Multi-AZ deployment. The company has a recovery time objective (RTO) of 15 minutes and a recovery point objective (RPO) of 1 hour for the database. During a recent disaster recovery drill, the solutions architect simulated an Availability Zone failure by terminating all EC2 instances and the primary RDS instance in one AZ. The Auto Scaling group launched new instances in the other AZ, and the RDS Multi-AZ failover completed in about 2 minutes. However, the application remained unavailable for 30 minutes because the new EC2 instances could not connect to the RDS secondary instance. The security groups are configured correctly. The RDS instance is not publicly accessible. What is the MOST likely cause of the connectivity issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Clue: "primary"
Why it matters: Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The application is using a hardcoded IP address or an endpoint that points to the old primary RDS instance instead of the RDS DNS name.
Option D is correct. The RDS Multi-AZ failover promotes the standby to primary, but the DNS record may take time to propagate. However, the more common issue is that the EC2 instances' security group or network ACL may be referencing the old primary's IP or the security group may not allow traffic to the new primary's IP. But given that security groups are correct, the likely issue is that the EC2 instances are using an endpoint that points to the old primary's DNS name or IP, which becomes invalid after failover. The RDS DNS name should be used (CNAME) that automatically points to the new primary. If the application uses a hardcoded IP or an endpoint that is not updated, connectivity fails. Option A is wrong because Multi-AZ failover typically completes within 1-2 minutes. Option B is wrong because the RDS endpoint DNS record updates quickly (within seconds). Option C is wrong because security groups are correctly configured.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The security group for the EC2 instances does not allow outbound traffic to the RDS instance.
Why it's wrong here
Security groups are stateful; outbound traffic is allowed by default.
✗
The RDS Multi-AZ failover took longer than expected, exceeding the RTO.
Why it's wrong here
The failover completed in 2 minutes, which is well within the 15-minute RTO.
✗
The RDS endpoint DNS record did not update to point to the new primary.
Why it's wrong here
DNS records update quickly, usually within seconds.
✓
The application is using a hardcoded IP address or an endpoint that points to the old primary RDS instance instead of the RDS DNS name.
Why this is correct
If the application does not use the RDS DNS name, it will try to connect to the old primary's IP, which is no longer available after failover.
Clue confirmation
The clue words "most likely", "primary" in the question point toward this answer.
Related concept
Static NAT maps one inside address to one outside address.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SAP-C02 NAT questions on configuration and troubleshooting.
Continuous Improvement for Existing Solutions — This question tests Continuous Improvement for Existing Solutions — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: The application is using a hardcoded IP address or an endpoint that points to the old primary RDS instance instead of the RDS DNS name. — Option D is correct. The RDS Multi-AZ failover promotes the standby to primary, but the DNS record may take time to propagate. However, the more common issue is that the EC2 instances' security group or network ACL may be referencing the old primary's IP or the security group may not allow traffic to the new primary's IP. But given that security groups are correct, the likely issue is that the EC2 instances are using an endpoint that points to the old primary's DNS name or IP, which becomes invalid after failover. The RDS DNS name should be used (CNAME) that automatically points to the new primary. If the application uses a hardcoded IP or an endpoint that is not updated, connectivity fails. Option A is wrong because Multi-AZ failover typically completes within 1-2 minutes. Option B is wrong because the RDS endpoint DNS record updates quickly (within seconds). Option C is wrong because security groups are correctly configured.
What should I do if I get this SAP-C02 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SAP-C02 NAT questions on configuration and troubleshooting.
Are there clue words in this question I should notice?
Yes — watch for: "most likely", "primary". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 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.
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.