A retail group runs a self-managed PostgreSQL 14 database on-premises that backs its order-management system, and the team wants a near zero-downtime migration into Cloud SQL for PostgreSQL with continuous replication from the existing primary until cutover. They will keep the source writable during the migration window and need a managed service that handles initial load and ongoing change capture without writing custom pipelines. Which Google Cloud service fits this role most directly?
- ABigQuery Data Transfer Service, configured with a PostgreSQL source connector to load the operational tables on a recurring schedule.
- BDatabase Migration Service, using a continuous migration job that performs an initial dump and then streams changes from the source PostgreSQL primary until promotion. Correct
- CDatastream, writing change events into Cloud Storage and then loading them into Cloud SQL with a scheduled Dataflow batch job.
- DTransfer Appliance, by exporting nightly base backups and write-ahead log archives onto the appliance and reloading them into Cloud SQL after ingestion.
Why A is wrong: BigQuery Data Transfer Service moves data into BigQuery from SaaS sources and a small set of databases, but its destination is BigQuery, not Cloud SQL, and it is built for analytics loads rather than transactional cutover with continuous replication.
Why B is correct: Database Migration Service is the managed homogeneous migration product for PostgreSQL and MySQL into Cloud SQL and AlloyDB, performing an initial load followed by continuous logical replication and a controlled promotion that minimises downtime at cutover.
Why C is wrong: Datastream captures change events from PostgreSQL but its supported destinations are BigQuery and Cloud Storage, not Cloud SQL, so reaching the operational target requires additional pipelines and gives up the managed cutover semantics of Database Migration Service.
Why D is wrong: Transfer Appliance is an offline bulk data shipping device for very large object datasets where network transfer is impractical, and it offers no continuous replication, so it cannot deliver the near zero-downtime cutover the team needs.