What change should the Database Specialist make to enable the migration?
Configure the on-premises application database to act as a source for an AWS DMS full load with ongoing change data capture (CDC)
Configure the AWS DMS replication instance to allow both full load and ongoing change data capture (CDC)
Configure the AWS DMS task to generate full logs to allow for ongoing change data capture (CDC)
Configure the AWS DMS connections to allow two-way communication to allow for ongoing change data capture (CDC)
Explanations:
Configuring the on-premises application database to act as a source for an AWS DMS full load with ongoing change data capture (CDC) allows the initial data to be loaded into RDS while simultaneously capturing changes made to the source database, ensuring minimal downtime when the RDS instance goes live.
While configuring the AWS DMS replication instance to allow both full load and ongoing change data capture (CDC) is important, this option does not specifically address how to minimize downtime during the migration process. The source database configuration is key for enabling CDC.
Configuring the AWS DMS task to generate full logs may assist with capturing changes, but it does not directly ensure the source database is set up for CDC. This option lacks the necessary context to guarantee minimal downtime for the migration.
Configuring the AWS DMS connections to allow two-way communication is unnecessary for the migration scenario described. CDC can be implemented without requiring two-way communication; thus, this option does not address the primary need for minimal downtime effectively.
In my experience, the answer is:
Configure the on-premises application database to act as a source for an AWS DMS full load with ongoing change data capture (CDC)