Examkin

Question

Difficulty: EasyDatabase Migration and Schema Conversion using DMS and SCT

A solutions architect is planning a heterogeneous database migration from an on-premises Oracle database to Amazon Aurora PostgreSQL using the AWS Schema Conversion Tool (SCT) and AWS Database Migration Service (DMS). To optimize the performance of the initial DMS full load phase and reduce target write latency, which action should the solutions architect take?

  1. A
    Deploy a single NAT Gateway in the public subnet and route all replication traffic from multiple Availability Zones through it to consolidate network bandwidth.
  2. B
    Provision an Amazon ElastiCache for Memcached cluster to act as a persistent replication cache between the source and target databases.
  3. Disable secondary indexes, foreign key constraints, and triggers on the target database before starting the full load, and re-enable them after completion.Answer
  4. D
    Enable supplemental logging or binary logging on the source database to accelerate the data transfer rate of the initial full load.

Answer

Disable secondary indexes, foreign key constraints, and triggers on the target database before starting the full load, and re-enable them after completion.
Disabling secondary indexes, foreign key constraints, and triggers on the target database before beginning a full load operation is a standard best practice to reduce write latency and maximize ingestion throughput. These components can be re-enabled and rebuilt once the full load phase completes.

Step-by-Step Solution

1
Identify the primary source of target database write latency during a bulk data load phase.
Secondary indexes, foreign keys, and triggers add significant write overhead for every inserted row.
By understanding that target database constraints and indexes slow down bulk inserts, we can plan to temporarily remove them.
2
Determine the configuration strategy to minimize target database overhead.
Disabling these constraints and indexes on the target before starting the full load task.
This allows DMS to perform high-speed bulk inserts without waiting for index updates or constraint validation.
3
Determine the post-load cleanup steps.
Re-enable foreign keys, triggers, and rebuild secondary indexes.
This ensures data integrity and query performance are restored once the bulk load is complete.

Key Concept

AWS Database Migration Service (DMS) full load optimization strategies
Rate this question

Topics

Database Migration and Schema Conversion using DMS and SCT

More questions from this topic