Examkin

Soru

Zorluk: KolayDatabase Migration and Schema Conversion using DMS and SCT

A solutions architect is using AWS Database Migration Service (DMS) to migrate an on-premises MySQL database to Amazon Aurora MySQL. The architect configures a replication task with both full load and continuous replication (Change Data Capture) enabled. The full load phase completes successfully, and all existing data is copied to the target database. However, subsequent insert and update transactions performed on the on-premises database are not replicated, and the task status stalls. Which of the following is the most likely cause of this behavior?

  1. Binary logging (binlog) was not enabled on the source MySQL database prior to starting the replication task.Cevap
  2. B
    The replication task attempted to write directly to a standby instance of a Multi-AZ deployment instead of the primary instance.
  3. C
    The migration was misclassified as refactoring, requiring the schema to be converted with the AWS Schema Conversion Tool (SCT) before continuous replication could begin.
  4. D
    TCP port 1500 was blocked on the source database server's firewall, preventing the replication agent from transmitting transaction logs.

Cevap

Binary logging (binlog) was not enabled on the source MySQL database prior to starting the replication task.
The correct answer is that binary logging (binlog) was not enabled on the source MySQL database. AWS Database Migration Service (DMS) uses the source database transaction logs (binary logs in MySQL) to capture and replicate ongoing transactions (CDC). Without binary logging enabled on the source, DMS has no way to track changes after the full load phase completes, resulting in a stalled or failed task.

Adım Adım Çözüm

1
Analyze the migration type and requirements.
The migration is homogeneous (MySQL to Aurora MySQL) and requires continuous replication (Change Data Capture).
This establishes that AWS DMS needs access to the source transaction engine logs to capture changes after the full load completes.
2
Identify the data source requirements for Change Data Capture (CDC) in AWS DMS.
For MySQL databases, DMS reads the binary logs (binlogs) to identify ongoing updates.
If binlogs are disabled, the task will succeed during the initial full load (which queries tables directly) but will fail to read transactions during the replication phase.
3
Evaluate the distractors based on the migration scenario.
Identify that other options describe port configurations for different services, incorrect RDS configurations, or unnecessary tool requirements.
This confirms that lack of source binlog configuration is the correct explanation for the stalled replication.

Anahtar Kavram

Continuous replication (CDC) using AWS DMS requires database-specific log configurations (such as binary logging for MySQL or supplemental logging for Oracle) to capture real-time changes.
Bu soruyu puanla

Konular

Database Migration and Schema Conversion using DMS and SCT

Bu konudan daha fazla soru