Examkin

Question

Difficulty: MediumManaging Technology Debt and Legacy Cloud Migrations

A global e-commerce analytics company is modernizing a legacy inventory management platform to resolve architectural technical debt during its migration to Google Cloud. The system relies on an on-premises 8 TB transactional PostgreSQL database with heavy read and write traffic. The legacy architecture suffers from significant tech debt, including hardcoded IP addresses embedded across legacy components and unversioned database schemas. The company requires a migration strategy that supports continuous data replication to achieve near-zero downtime (under 15 minutes cutover) while decoupling application components from hardcoded database IP endpoints without modifying the legacy core code. Which migration architecture should the cloud architect recommend?

  1. Utilize Database Migration Service (DMS) to establish continuous change data capture (CDC) replication from the legacy PostgreSQL database to Cloud SQL for PostgreSQL, and implement Private Service Connect alongside Cloud DNS private zone entries to abstract endpoint IP addresses prior to cutover.Answer
  2. B
    Migrate the legacy PostgreSQL database to Cloud Spanner by configuring custom batch export pipelines to continuously stream transactional logs until the planned cutover window.
  3. C
    Order a Google Cloud Transfer Appliance to capture an offline snapshot of the 8 TB PostgreSQL database, ship the appliance to Google Cloud, and restore the database instance into Cloud SQL during the maintenance window.
  4. D
    Containerize the legacy PostgreSQL database engine and deploy it onto Google Kubernetes Engine (GKE) using StatefulSets with host networking to preserve existing IP address mappings.

Answer

Utilize Database Migration Service (DMS) to establish continuous change data capture (CDC) replication from the legacy PostgreSQL database to Cloud SQL for PostgreSQL, and implement Private Service Connect alongside Cloud DNS private zone entries to abstract endpoint IP addresses prior to cutover.
Database Migration Service (DMS) enables serverless, low-friction migration to Cloud SQL using native PostgreSQL replication and Change Data Capture (CDC), fulfilling the requirement for near-zero downtime cutover. Pairing Cloud SQL with Private Service Connect and Cloud DNS private zones abstracts database endpoints, resolving legacy technical debt stemming from hardcoded IP addresses.

Step-by-Step Solution

1
Analyze the database migration requirements and constraints.
Identified an 8 TB PostgreSQL workload requiring continuous replication (under 15-minute cutover) and a mechanism to resolve hardcoded IP technical debt.
Managed replication services like DMS allow continuous CDC synchronization from source to target without long downtime.
2
Evaluate Google Cloud managed target services.
Selected Cloud SQL for PostgreSQL as the fully managed destination, eliminating self-management overhead.
Cloud SQL maintains engine compatibility with existing PostgreSQL schemas, avoiding complex application refactoring.
3
Address legacy endpoint technical debt.
Implemented Cloud DNS private zones and Private Service Connect to route traffic via DNS hostnames rather than hardcoded IPs.
Abstracting IP addresses through private DNS entries allows seamless cutover without updating application source code.

Key Concept

Managing Database Technical Debt and Low-Downtime Migration Patterns
Rate this question

Topics

Managing Technology Debt and Legacy Cloud Migrations

More questions from this topic