A data engineer is using AWS Database Migration Service (AWS DMS) to migrate a 4 TB on-premises Oracle database to Amazon Aurora PostgreSQL. The migration must complete in a single maintenance window, and the source database cannot be taken offline for more than 30 minutes. The engineer configures a full load plus change data capture (CDC) task. During testing, the full load phase takes 14 hours. Which configuration change will most effectively reduce the time required for the full load phase?
AWS DMS supports parallel full load, which loads multiple tables simultaneously instead of serially. For a 4 TB Oracle database with many tables, increasing the number of tables loaded concurrently in the task settings significantly reduces overall full load time by using multiple threads and network connections. This is the most effective and supported tuning mechanism for reducing full load duration without changing the source or target.
Why this answer
Parallel full load is the primary DMS tuning lever for reducing bulk migration time. By loading multiple tables concurrently, DMS saturates available network and I/O resources rather than processing tables serially. Switching to CDC only would skip existing data entirely, and scaling the target or enabling Multi-AZ does not address the serial loading bottleneck that dominates a large full load.
Exam trap
The trap here is assuming that scaling the target database or enabling high availability will speed up a DMS full load, when the real bottleneck is the serial table-by-table loading that parallel load addresses.