PDE Practice Question: Drag and drop the steps to migrate an on-premises…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  First, prepare the source database by enabling binary logging and creating a replication user. Second, create a target Cloud SQL instance. Third, create a connection profile in Database Migration Service. Fourth, create and start the migration job, then perform the final cutover (promote Cloud SQL).

  Why this is correct

  This sequence follows the official Google Cloud documentation. Preparing the source ensures replication readiness, the target instance must exist before the migration job, the connection profile defines the source, and the job performs the migration with minimal downtime.

• ✗

  First, create a target Cloud SQL instance. Second, prepare the source database by enabling binary logging and creating a replication user. Third, create a connection profile in Database Migration Service. Fourth, create and start the migration job, then perform the final cutover.

  Why it's wrong here

  This order is incorrect because the source must be prepared before creating the connection profile (which references the source), but creating the target before preparing the source may cause delays or misconfiguration. The target can be created at any time before the migration job, but preparing the source first is more logical.

• ✗

  First, prepare the source database by enabling binary logging and creating a replication user. Second, create a connection profile in Database Migration Service. Third, create a target Cloud SQL instance. Fourth, create and start the migration job, then perform the final cutover.

  Why it's wrong here

  This order is incorrect because the target Cloud SQL instance must exist before the migration job can reference it. Creating the connection profile before the target instance is possible, but the migration job creation requires both, so it's inefficient and may cause errors.

• ✗

  First, prepare the source database by enabling binary logging and creating a replication user. Second, create and start the migration job, then perform the final cutover. Third, create a target Cloud SQL instance. Fourth, create a connection profile in Database Migration Service.

  Why it's wrong here

  This order is incorrect because the migration job cannot be created without a target instance and a connection profile. Performing the cutover before creating the target makes no sense. The steps are completely out of logical order.