A company wants to migrate its MySQL database from on premises to AWS. The company recently experienced a database outage that significantly impacted the business. To prevent recurrence, the company wants a reliable database solution on AWS that minimizes data loss and ensures every transaction is stored on at least two nodes. Which solution meets these requirements?

The correct solution is to create an Amazon RDS MySQL DB instance with Multi-AZ functionality enabled. Multi-AZ deployments for Amazon RDS provide high availability and durability by synchronously replicating data to a standby instance in a different Availability Zone. This ensures that every transaction is committed to both instances before being acknowledged, minimizing data loss and providing automatic failover in case of an outage. Creating an Amazon RDS DB instance with synchronous replication to three nodes in three Availability Zones is not a standard RDS feature for MySQL and overcomplicates the solution. Creating a read replica in a separate AWS Region provides disaster recovery but read replicas are asynchronously replicated, meaning there could be data loss during a regional outage. Using an Amazon EC2 instance with a MySQL engine and a Lambda function for synchronous replication is a custom, complex solution that doesn't offer the built-in reliability and managed features of RDS Multi-AZ.