Answer-first summary for fast verification
Answer: Implement routinely scheduled failovers of your databases
The question focuses on preventing the failure of automatic failover when the primary database crashes during peak traffic. Option D (Implement routinely scheduled failovers) is the correct choice because it proactively tests the failover mechanism, ensuring the replica can be promoted successfully when needed. This addresses the core issue of untested failover processes, as highlighted by the community consensus (67% support for D, with high upvotes on comments advocating for D). While option B (Choose larger instances) might reduce crashes due to resource constraints, it does not guarantee the replica will be promoted, and the crash cause is unspecified—larger instances could still fail or overlook failover flaws. Options A and C are irrelevant: A (different database) doesn't fix failover testing, and C (regular snapshots) aids backups but not promotion reliability. Thus, D is optimal for resilience and disaster recovery best practices.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have a relational database that crashes during peak traffic periods, but its replica fails to be promoted to primary. How do you prevent this from happening again?
A
Use a different database
B
Choose larger instances for your database
C
Create snapshots of your database more regularly
D
Implement routinely scheduled failovers of your databases
No comments yet.