A company needs to migrate an Amazon Aurora MySQL DB cluster from one AWS account to a new AWS account in the same Region. Both accounts are in the same AWS Organization. The company wants to minimize database service interruption before switching DNS to the new database. Which migration strategies meet this requirement? (Choose two.)

Taking and sharing an Aurora snapshot allows for a point-in-time copy of the database to be restored in the new account. While this involves some downtime for the initial snapshot, the new cluster can be provisioned and tested independently, minimizing service interruption during the DNS switch. AWS DMS is designed for migrating databases with minimal downtime. It can perform a full load of the source database to the target and then continuously replicate changes, allowing for a seamless cutover when the target database is fully synchronized. AWS Backup is not the primary mechanism for cross-account Aurora cluster migration; while it can back up Aurora, restoring to a different account for migration purposes is less direct than snapshot sharing or DMS. AWS Application Migration Service (AWS MGN) is for migrating entire servers or applications, not specifically for migrating data between two Aurora DB clusters.