Question

Difficulty: MediumDatabase Migration and Schema Conversion using DMS and SCT

A company is planning to migrate an on-premises Microsoft SQL Server database to an Amazon Aurora MySQL-Compatible Edition DB cluster. The migration must support ongoing replication to minimize cutover downtime. The source database contains several tables with VARBINARY(MAX) columns storing documents, where some individual records exceed 2 MB in size. A Solutions Architect is setting up AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS) to execute this migration.

Which TWO configurations must the Solutions Architect implement to ensure successful data replication with minimal downtime? (Select TWO.)

  1. Enable Microsoft Change Data Capture (MS-CDC) on the source SQL Server database and the tables selected for migration.Answer
  2. Configure the AWS DMS replication task to use Limited LOB mode and set the Max LOB size parameter to at least 4096 KB.Answer
  3. C
    Configure the source SQL Server endpoint in AWS DMS to read directly from active transaction logs without enabling database-level MS-CDC.
  4. D
    Configure the AWS DMS replication task to use Full LOB mode with inline LOBs enabled to replicate all VARBINARY(MAX) columns.
  5. E
    Install the AWS SCT agent on the replication instance to handle the translation of LOB data types dynamically during the replication phase.

Answer

Enable Microsoft Change Data Capture (MS-CDC) on the source SQL Server database and the tables selected for migration, and configure the AWS DMS replication task to use Limited LOB mode with the Max LOB size parameter set to at least 4096 KB.
To support continuous replication (CDC) from Microsoft SQL Server, Microsoft Change Data Capture (MS-CDC) must be enabled on the source database and tables so AWS DMS can read ongoing changes from the transaction logs. Additionally, to handle Large Objects (LOBs) such as documents in VARBINARY(MAX) columns that exceed 2 MB, the AWS DMS task should be configured with Limited LOB mode and a Max LOB size set to at least 4096 KB to accommodate the largest files without truncation or task failure, while preserving replication performance.

Step-by-Step Solution

1
Enable Microsoft Change Data Capture (MS-CDC) on the source database.
Ongoing changes can be tracked in the SQL Server transaction logs.
AWS DMS requires MS-CDC to capture ongoing changes (Change Data Capture) from a SQL Server source database.
2
Configure LOB settings in the AWS DMS replication task.
Limited LOB mode is selected with a Max LOB size of 4096 KB.
Since the source database contains LOB data (documents in VARBINARY(MAX) columns) that exceed 2 MB (2048 KB), the Max LOB size must be set higher than the largest LOB (e.g., 4096 KB) to prevent truncation errors while maintaining optimal performance.

Key Concept

Continuous replication with AWS DMS requires enabling source-side logging (MS-CDC for SQL Server) and configuring task parameters (such as LOB settings) to handle large data types appropriately.
Rate this question