Learn how to implement a disaster recovery solution for your Amazon RDS databases by creating read replicas in different AWS regions and automating failover using Lambda functions, ensuring data integrity and business continuity.
Table of Contents
Question
A company has applications that process transaction requests multiple times each minute. The applications write transaction data to a single Amazon RDS DB instance. As the company begins to process more transactions, the company becomes concerned that it has no failover solution in place for disaster recovery (DR). The company needs the DB instance to fail over automatically without losing any committed transactions.
Which solution will meet these requirements?
A. Create an RDS read replica in the same AWS Region. Configure an AWS Lambda function to promote the replica as the primary DB instance during a DR scenario.
B. Create an RDS read replica in a different AWS Region. Configure an AWS Lambda function to promote the replica as the primary DB instance during a DR scenario.
C. Modify the DB instance to be a Multi-AZ deployment.
D. Setup an Amazon CloudWatch alarm that monitors the DB instance memory utilization with a threshold greater than 90%. Invoke an AWS Lambda function to restart the DB instance.
Answer
B. Create an RDS read replica in a different AWS Region. Configure an AWS Lambda function to promote the replica as the primary DB instance during a DR scenario.
Explanation
By creating an Amazon RDS read replica in a different AWS Region, the company can establish a disaster recovery solution that ensures automatic failover without losing committed transactions in the event of a regional outage or disaster.
Here’s how this solution works:
- In the primary AWS Region, create an Amazon RDS DB instance to serve as the production database.
- In a different AWS Region (e.g., a geographically distant region), create an RDS read replica of the production DB instance. This read replica will be continuously updated with the latest data from the primary instance.
- Configure an AWS Lambda function that can promote the read replica to a standalone DB instance (the new primary) when invoked. This Lambda function should be deployed in the same region as the read replica.
- Set up monitoring and alerting mechanisms to detect a failure or unavailability of the primary DB instance in the production region.
- When a failure is detected, invoke the Lambda function to promote the read replica to a standalone DB instance, effectively making it the new primary DB instance.
By having a read replica in a separate region, the company can failover to the replica without data loss in case of a regional disaster or outage affecting the primary DB instance. The Lambda function automates the promotion of the read replica, ensuring a seamless transition to the new primary DB instance.
Other options do not meet the requirements:
A. Creating a read replica in the same region does not provide disaster recovery protection against regional outages. C. A Multi-AZ deployment provides high availability within the same region but does not provide cross-region failover capabilities. D. Restarting the DB instance based on memory utilization does not address the need for automatic failover and disaster recovery.
Amazon AWS Certified SysOps Administrator – Associate certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Amazon AWS Certified SysOps Administrator – Associate exam and earn Amazon AWS Certified SysOps Administrator – Associate certification.