A company is migrating a three-tier application to AWS that requires a MySQL database. Previously, users experienced poor performance creating new entries because users generated different real-time reports during working hours. Which solution will improve application performance after the migration to AWS?

The correct solution is to create an Amazon Aurora MySQL Multi-AZ DB cluster with multiple read replicas and configure the application to use the reader endpoint for reports. This directly addresses the performance issue of generating real-time reports during working hours. Aurora read replicas offload read-heavy workloads, like reports, from the primary instance, allowing the primary to efficiently handle write operations (creating new entries). The reader endpoint automatically distributes connections across available read replicas, improving scalability and availability. Importing data into DynamoDB would require significant application refactoring and might be overkill if the primary issue is read scalability for an existing relational database. Creating the database on a compute-optimized EC2 instance doesn't inherently solve the read-write contention problem; it only provides more compute for the single instance. Using the cluster's backup instance for reports is incorrect as backup instances are for disaster recovery, not for serving live read traffic.