You are migrating your critical production database from Amazon RDS for MySQL to Cloud SQL for MySQL by using Google Cloud's Database Migration Service. You want to keep disruption to your…

Question

Options

• ACreate and start multiple Database Migration Service jobs to migrate your database to the target
• BUpgrade the Amazon RDS for MySQL primary instance to an instance with more vCPUs and
• CCreate a single Database Migration Service migration job with initial load parallelism configured to
• DCreate a single Database Migration Service migration job with initial Load Parallelism configured to

Explanation

The correct answer is C. A single Database Migration Service job with initial load parallelism configured to use multiple parallel threads optimizes migration throughput while minimizing disruption. Using a single job avoids race conditions, duplicate data risks, and conflicting transactions that arise with multiple simultaneous migration jobs targeting the same destination. Configuring parallelism within that single job allows DMS to read from the source (RDS) and write to the target (Cloud SQL) concurrently across multiple table segments, significantly accelerating the initial full load. Option A (multiple DMS jobs) risks data conflicts and is not a supported best practice. Option B (upgrading the RDS instance) changes the source infrastructure, adding cost and potential disruption without addressing migration configuration. Option D typically refers to a parallelism setting that is too aggressive and can overload the source RDS instance.

No community discussion yet for this question.