Examkin

Question

Difficulty: HardManaging Technology Debt and Legacy Cloud Migrations

A global telecommunications enterprise is migrating its legacy billing and subscription management platform from an on-premises data center to Google Cloud. The architecture consists of a 12 TB single-region PostgreSQL relational database with historical technical debt and a set of simple, stateless HTTP web services that process customer subscription requests.

The organization mandates a phased migration strategy with zero data loss and minimal operational maintenance after migration. The existing on-premises network link is a low-bandwidth Cloud VPN connection that cannot sustain continuous database replication alongside daily production traffic.

Which combination of Google Cloud services and migration patterns best addresses the technical debt, network bandwidth constraints, and operational goals?

  1. Provision a Dedicated Interconnect connection, use Database Migration Service (DMS) for continuous Change Data Capture (CDC) to Cloud SQL for PostgreSQL, and deploy the stateless HTTP microservices to Cloud Run.Answer
  2. B
    Migrate the on-premises database to Cloud Spanner using custom data export scripts, and host the stateless HTTP microservices on a multi-zone Google Kubernetes Engine (GKE) Enterprise cluster.
  3. C
    Order a Google Cloud Transfer Appliance to physically import the 12 TB database backup, and deploy the stateless HTTP microservices to Google Kubernetes Engine (GKE) using Autopilot mode.
  4. D
    Establish a Dedicated Interconnect, migrate the PostgreSQL database to Cloud SQL using Database Migration Service (DMS), and configure HA VPN over Dedicated Interconnect while granting primitive Editor roles to the application service account to simplify network resource provisioning.

Answer

Provision a Dedicated Interconnect connection, use Database Migration Service (DMS) for continuous Change Data Capture (CDC) to Cloud SQL for PostgreSQL, and deploy the stateless HTTP microservices to Cloud Run.
The solution effectively resolves technical debt and migration constraints by establishing a Dedicated Interconnect for reliable high-speed data transfer, utilizing Database Migration Service (DMS) for continuous CDC to Cloud SQL for PostgreSQL to achieve zero-downtime migration, and deploying stateless microservices to Cloud Run to eliminate cluster management overhead.

Step-by-Step Solution

1
Analyze database migration and replication requirements
Database Migration Service (DMS) with continuous CDC allows minimal-downtime migration of a PostgreSQL instance to Cloud SQL PostgreSQL without requiring global multi-region database refactoring.
Cloud SQL maintains relational operational compatibility while eliminating database infrastructure maintenance debt. Cloud Spanner is unnecessary for single-region relational needs.
2
Evaluate hybrid connectivity and bandwidth constraints
Dedicated Interconnect provides high-bandwidth, reliable private connectivity required to transport bulk database snapshots and handle continuous CDC replication without overwhelming existing low-bandwidth VPN links.
Physical Transfer Appliance shipping cannot support continuous online CDC replication needed for zero-downtime cutover.
3
Select appropriate compute platform for legacy stateless HTTP services
Cloud Run provides fully managed serverless execution for stateless containerized web services with automatic scaling and zero infrastructure management.
Using GKE for basic stateless microservices adds management overhead and baseline cluster costs, representing infrastructure technical debt.

Key Concept

Managing Technology Debt and Legacy Cloud Migrations
Rate this question

Topics

Managing Technology Debt and Legacy Cloud Migrations

More questions from this topic