Examkin

Question

Difficulty: MediumDatabase Migration and Schema Conversion using DMS and SCT

A solutions architect is planning the heterogeneous migration of a production on-premises MySQL database to an Amazon Aurora PostgreSQL-Compatible Edition DB cluster. The migration must minimize downtime, and the database experiences high write activity. The solutions architect has already run the AWS Schema Conversion Tool (SCT) to convert the database schema. To complete the migration, AWS Database Migration Service (DMS) will be used with Change Data Capture (CDC) enabled.

Which two actions must the solutions architect perform to prepare the source database and ensure successful CDC replication? (Select two.)

  1. Configure the MySQL configuration file on the source database to set binlog_format to ROW and binlog_row_image to FULL.Answer
  2. Configure the source database to retain binary logs for a minimum of 24 hours to prevent data loss before AWS DMS processes them.Answer
  3. C
    Configure the MySQL source database to set binlog_format to STATEMENT to optimize write performance and reduce log storage size.
  4. D
    Configure the AWS Schema Conversion Tool (SCT) data agent to capture database changes in real time and apply them to the target cluster.
  5. E
    Configure the target Aurora PostgreSQL DB cluster to run in MySQL compatibility mode to avoid converting the database schema.

Answer

To perform successful Change Data Capture (CDC) from an on-premises MySQL database to Amazon Aurora PostgreSQL, you must set the source parameters binlog_format to ROW and binlog_row_image to FULL. Additionally, the source database must be configured to retain its binary logs for at least 24 hours to prevent replication errors.
To successfully perform Change Data Capture (CDC) from an on-premises MySQL database using AWS DMS, row-based logging must be enabled by setting the binary log format to ROW and the binary log row image to FULL. Additionally, the source database must be configured to retain these binary logs for a sufficient duration (typically at least 24 hours) to prevent the log files from being purged before AWS DMS can read and apply the changes.

Step-by-Step Solution

1
Configure source binary logging parameters
Setting binlog_format to ROW and binlog_row_image to FULL ensures the necessary row-level change detail is logged.
AWS DMS requires detailed row-level change information in the binary logs to perform CDC replication from MySQL.
2
Configure binary log retention policy on the source
Configuring the retention to at least 24 hours prevents logs from being purged before they are consumed by the DMS replication task.
High-write environments generate large amounts of logs; if the retention period is too short, DMS will miss changes, causing the task to fail.
3
Verify schema conversion and launch DMS task
The target schema is already converted via SCT, and the DMS task starts replicating data from the source to the target.
DMS requires the schema to be present on the target before replicating data, and then relies on the configured binlogs to perform ongoing replication.

Key Concept

Configuring MySQL source databases for Change Data Capture (CDC) replication using AWS DMS requires setting specific binary logging configurations (ROW format and FULL row image) and ensuring binary logs are retained long enough to prevent replication failures.
Estimated Time:2m 0s
Rate this question

Topics

Database Migration and Schema Conversion using DMS and SCT

More questions from this topic