A company's database specialist is migrating a production Amazon RDS for MySQL database to Amazon Aurora MySQL. The source database is configured for Multi-AZ. The company's production team wants to v

Enabling automatic backups on the source RDS database is a critical best practice to ensure data recovery and safety during any migration process, even though it doesn't directly enable DMS.

Disabling automatic backups on a production database before or during a migration is a poor practice that increases the risk of data loss.

AWS DMS requires binary logging to be enabled on the MySQL source database to capture change data for continuous replication, and setting the `binlog_format` parameter to `ROW` is generally recommended for data consistency and integrity during replication tasks.

While binary logging is essential, setting the `binlog_format` to `ROW` (as in option C) is generally the preferred and more robust choice for AWS DMS replication tasks to ensure data accuracy compared to `MIXED`.

When using AWS DMS with an Amazon RDS Multi-AZ source, the DMS task must use the primary database instance as its source endpoint to capture all writes and replicate them to the target.

AWS DMS tasks are configured to connect to the primary instance of an RDS Multi-AZ deployment to capture changes, not the secondary (standby) instance.