A Database Specialist is migrating an on-premises Microsoft SQL Server application database to Amazon RDS for PostgreSQL using AWS DMS. The application requires minimal downtime when the RDS DB…

Question

Options

• AConfigure the on-premises application database to act as a source for an AWS DMS full load with
• BConfigure the AWS DMS replication instance to allow both full load and ongoing change data
• CConfigure the AWS DMS task to generate full logs to allow for ongoing change data capture
• DConfigure the AWS DMS connections to allow two-way communication to allow for ongoing

• A
  80% (35)
• B
  5% (2)
• C
  5% (2)
• D
  11% (5)

Explanation

Explanation

Option A is correct because configuring the on-premises SQL Server database as a source with CDC (Change Data Capture) enabled allows AWS DMS to perform a full initial load and then continuously replicate ongoing changes, keeping the source and target in sync until cutover - this minimizes downtime to just the brief moment of final switchover.

Option B is incorrect because the replication instance is simply the compute resource that runs DMS tasks; enabling CDC is a configuration on the DMS task and source database, not the replication instance itself. Option C is incorrect because generating "full logs" on the DMS task is not a valid or sufficient mechanism for enabling CDC - proper transaction log settings must be configured at the source database level. Option D is incorrect because DMS migrations are inherently one-directional (source → target), and two-way communication is not a feature DMS offers for this use case.

Memory Tip: Think of the phrase "Load then Listen" - a minimal downtime migration requires the source to first do a full load, then listen for changes via CDC. The source database must be enabled to talk, so always start the configuration at the source.

No community discussion yet for this question.