Examkin

Question

Difficulty: HardDatabase Migration and Schema Conversion using DMS and SCT

A financial services company is planning to migrate its on-premises self-managed PostgreSQL 14 database containing large tables with complex PL/pgSQL stored procedures to an Amazon Aurora MySQL-Compatible Edition DB cluster. The migration must minimize downtime and ensure continuous replication during the transition period. The company also wants to analyze schema compatibility and perform conversion before starting the data transfer. Which of the following actions should the Solutions Architect take to configure this migration? (Select two.)

  1. Use the AWS Schema Conversion Tool (SCT) to generate a migration assessment report and convert the database schema, including PL/pgSQL stored procedures, to equivalent MySQL structures.Answer
  2. Configure the on-premises PostgreSQL source database by setting the wal_level parameter to logical and increasing max_replication_slots and max_wal_senders to enable Change Data Capture (CDC) replication in AWS DMS.Answer
  3. C
    Enable binary logging on the on-premises PostgreSQL database by setting the binlog_format parameter to ROW and enabling supplemental logging for all tables.
  4. D
    Perform a Replatform migration by directly using AWS DMS to automatically convert the source PostgreSQL schemas, custom types, and stored procedures to Aurora MySQL format during the initial data load.
  5. E
    Configure an AWS DMS task with Full Load only, and use an AWS Lambda function triggered by Amazon EventBridge to manually scan the source database for incremental changes using timestamp columns to minimize source database performance impact.

Answer

Use the AWS Schema Conversion Tool (SCT) to convert the schema and stored procedures, and configure the source PostgreSQL database parameters (wal_level to logical, max_replication_slots, and max_wal_senders) to support continuous Change Data Capture (CDC) replication.
The correct options are using the AWS Schema Conversion Tool (SCT) to perform the schema translation for the heterogeneous migration, and configuring PostgreSQL's native logical replication parameters (wal_level, max_replication_slots, max_wal_senders) on the source database to support Change Data Capture (CDC) replication.

Step-by-Step Solution

1
Use AWS SCT to perform schema analysis and conversion.
The AWS Schema Conversion Tool converts the PostgreSQL schemas, functions, and stored procedures to their MySQL equivalents and outputs a migration assessment report showing any manual adjustments required.
Because PostgreSQL to Aurora MySQL is a heterogeneous migration, AWS DMS cannot convert the schema structures and code objects automatically.
2
Configure PostgreSQL replication parameters for CDC.
Set wal_level to logical, configure max_replication_slots and max_wal_senders to be greater than 1, and grant replication permissions to the database user.
This enables PostgreSQL to store transaction logs for logical decoding, which AWS DMS reads during the Change Data Capture (CDC) phase to replicate ongoing changes.
3
Create and run the AWS DMS task.
Launch a replication task configured for Full Load and Change Data Capture (CDC) using the converted schema target.
This ensures that initial data is loaded and subsequent changes are synchronized in real-time, minimizing downtime during the eventual cutover.

Key Concept

Heterogeneous database migration using SCT for schema translation and DMS logical replication settings (wal_level, replication slots) for continuous replication (CDC).
Rate this question

Topics

Database Migration and Schema Conversion using DMS and SCT

More questions from this topic