Which solution will provide the HIGHEST availability for the database?
Configure automated backups on Amazon RDS. In the case of disruption, promote an automated backup to be a standalone DB instance. Direct database traffic to the promoted DB instance. Create a replacement read replica that has the promoted DB instance as its source.
Configure global tables and read replicas on Amazon RDS. Activate the cross-Region scope. In the case of disruption, use AWS Lambda to copy the read replicas from one Region to another Region.
Configure global tables and automated backups on Amazon RDS. In the case of disruption, use AWS Lambda to copy the read replicas from one Region to another Region.
Configure read replicas on Amazon RDS. In the case of disruption, promote a cross-Region and read replica to be a standalone DB instance. Direct database traffic to the promoted DB instance. Create a replacement read replica that has the promoted DB instance as its source.
Explanations:
While configuring automated backups is important for recovery, promoting a backup to a standalone DB instance does not provide the same level of availability as using read replicas. This option lacks redundancy and immediate failover capabilities, making it less ideal for high availability.
Amazon RDS does not support global tables like DynamoDB, and copying read replicas across Regions with AWS Lambda is not a straightforward or effective way to ensure high availability. This approach would lead to potential data inconsistency and increased latency.
Similar to option B, Amazon RDS does not support global tables. Automated backups do not provide immediate availability during a disruption. Copying read replicas across Regions with Lambda introduces complexities and risks in data integrity and availability.
This option involves configuring read replicas, including cross-Region read replicas that can be promoted during a disruption. Promoting a read replica allows for near-instantaneous failover, providing a high availability solution. This method ensures minimal downtime and continuous operation of the database.