A company’s applications write transaction data multiple times per minute to a single Amazon RDS DB instance. As transaction volume grows, the company needs automatic failover for disaster recovery that preserves committed transactions. Which solution meets this need?

Converting the DB instance to a Multi-AZ RDS deployment is the correct solution because it provides automatic failover with data durability. In a Multi-AZ deployment, Amazon RDS automatically provisions and maintains a synchronous standby replica in a different Availability Zone. If the primary DB instance fails, RDS automatically fails over to the standby replica, preserving committed transactions without manual intervention. Creating a read replica in the same or a different Region (options 1 and 2) requires manual promotion via a Lambda function during a DR event, which introduces recovery time and potential data loss if the primary fails before the replica is fully caught up. A CloudWatch alarm to restart the DB instance (option 4) addresses performance issues, not disaster recovery or automatic failover, and would cause downtime.