Mitigating RDS Single Point of Failure with Least Effort

SAA-C03 By islever Editorial Last updated

Design secure access to AWS resources.

Short answer

A Modify the RDS DB instance to use a Multi-AZ deployment to enable automatic failover with minimal changes.

Question

A company hosts an ecommerce application that stores all data in a single Amazon RDS for MySQL DB instance that is fully managed by AWS. The company needs to mitigate the risk of a single point of failure. Which solution will meet these requirements with the LEAST implementation effort?
  1. Modify the RDS DB instance to use a Multi-AZ deployment. Apply the changes during the next maintenance window. Correct Answer
  2. Migrate the current database to a new Amazon DynamoDB Multi-AZ deployment. Use AWS Database Migration Service (AWS DMS) with a heterogeneous migration strategy to migrate the current RDS DB instance to DynamoDB tables.
  3. Create a new RDS DB instance in a Multi-AZ deployment. Manually restore the data from the existing RDS DB instance from the most recent snapshot.
  4. Configure the DB instance in an Amazon EC2 Auto Scaling group with a minimum group size of three. Use Amazon Route 53 simple routing to distribute requests to all DB instances.

Key Takeaways

The exam focuses on distinguishing between high availability (Multi-AZ) and disaster recovery/backups, with the common trap being complex migrations or manual restores when a simple configuration change suffices.

This question tests how to eliminate a single point of failure for an Amazon RDS MySQL instance while minimizing implementation effort. The correct approach is enabling Multi-AZ deployment directly on the existing instance.

Common mistake: Candidates often choose option C (manual restore from snapshot) because they overthink the 'new instance' requirement or misunderstand that Multi-AZ can be enabled on an existing instance without data loss or complex migration steps.

Expert Analysis

Why the Answer Is Correct

Option A is the correct answer because Amazon RDS Multi-AZ deployments provide automatic failover support, which mitigates the risk of a single point of failure by maintaining a synchronous standby replica in a different Availability Zone. Enabling this feature on an existing DB instance involves minimal implementation effort compared to migrating to NoSQL or manually restoring snapshots, as AWS handles the setup and replication transparently.

Why the Other Options Are Wrong

Option B suggests migrating to DynamoDB, which is a significant architectural change requiring application code refactoring and data migration, thus failing the 'least implementation effort' criteria. Option C involves creating a new instance and manually restoring data, which is more labor-intensive than simply modifying the existing instance settings and introduces potential data inconsistency if not done carefully. Option D proposes running RDS instances inside an EC2 Auto Scaling group, which is technically invalid as RDS is a managed service and cannot be deployed as standard EC2 instances within an ASG; additionally, Route 53 simple routing does not provide health-based failover suitable for database connections.

Community Comment Notes

Community feedback strongly supports Option A, with users noting that it provides automated failover and high availability with minimal effort. One commenter explicitly stated that 'Answer is A', reinforcing the consensus that no complex migration is needed for this specific HA requirement.

Official Reference

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

Always look for the path of least resistance when 'least implementation effort' is specified. For RDS, enabling Multi-AZ is a configuration toggle, whereas migrations or manual restores involve operational overhead.

Frequently Asked Questions

Can I enable Multi-AZ on an existing RDS instance?

Yes, you can modify an existing RDS instance to enable Multi-AZ deployment during a maintenance window or immediately.

Why is DynamoDB not the best choice here?

Migrating to DynamoDB requires schema redesign and application changes, which contradicts the 'least implementation effort' requirement.

More SAA-C03 FAQ →

Community Votes

A
100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. example_ 👍 5 Answered A
    https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html
  2. Changwha 👍 2
    A: This solution provides automated failover and high availability with minimal implementation effort.
  3. komorebi 👍 2 Answered A
    Answer is A

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide