A company has LAMP (Linux, Apache, MySQL, PHP) stack applications deployed to AWS.The availability requirements for its backend database specify automatic failover in case of disaster recovery.What is the optimal solution that meets this requirement?

Answer options:

A.RDS with Multi-AZ deployment
B.RDS with Read-Replica deployment
C.DynamoDB with Global Tables deployment
D.Deploy multiple RDS instances.Use Route53 with Health-Check and DNS failover configured

Answer: A
Option A is CORRECT because with RDS Multi-AZ deployment, a primary DB instance is automatically and synchronously replicated to a secondary RDS instance in a different availability zone (AZ).In case of a disaster causing primary instance failure, RDS performs an automatic failover to the standby RDS instance.
Option B is incorrect because RDS Read-Replica provides secondary RDS instances that are asynchronously replicated from the primary.RDS read-replicas have different endpoints and do not provide automatic failover.Additionally, they only provide read (not write) operations.
Option C is incorrect. Since the scenario calls for MySQL, we must choose a relational database for the backend database.
Option D is incorrect because this solution does not provide automatic data synchronization between instances.
Reference:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html