Examkin

Question

Difficulty: MediumManaging Technology Debt and Legacy Cloud Migrations

A fintech enterprise is modernizing a legacy online payment portal to eliminate architectural technical debt during its migration from an on-premises data center to Google Cloud. The application architecture consists of lightweight, stateless HTTP API microservices and a standard single-region 3 TB relational database. The migration strategy mandates minimizing operational management overhead for compute while maintaining backward compatibility for database schema updates to support continuous rollout without downtime.

Which TWO architectural actions should the team take to achieve these requirements? (Select TWO)

  1. Deploy the stateless HTTP API microservices to Cloud Run.Answer
  2. Migrate the database to Cloud SQL using Database Migration Service (DMS) and implement an expand-and-contract schema pattern during migration.Answer
  3. C
    Deploy the stateless HTTP API microservices on a dedicated Google Kubernetes Engine (GKE) Standard cluster with cluster autoscaling.
  4. D
    Migrate the relational database directly to Cloud Spanner to handle standard single-region database operations.

Answer

The team should deploy the stateless HTTP microservices to Cloud Run and migrate the relational database to Cloud SQL using Database Migration Service (DMS) while leveraging an expand-and-contract schema pattern.
Deploying stateless microservices to Cloud Run minimizes operational management by using a fully managed serverless execution model. Migrating the relational database to Cloud SQL using Database Migration Service provides a streamlined migration path, while using an expand-and-contract schema pattern ensures zero-downtime schema migrations that maintain backward compatibility across old and new application versions.

Step-by-Step Solution

1
Evaluate compute modernization choices against technical debt and operational overhead constraints.
Cloud Run provides a fully managed serverless compute environment for containerized stateless HTTP microservices without requiring node provisioning or cluster control plane management.
Choosing GKE for simple stateless services creates unnecessary operational complexity and maintenance burden.
2
Select database destination and continuous replication migration tooling.
Cloud SQL provides managed relational database capabilities suitable for single-region workload sizes, managed seamlessly via Database Migration Service (DMS).
Cloud Spanner is designed for globally distributed scale and adds unnecessary cost and refactoring overhead for standard single-region relational databases.
3
Define database schema migration strategy to ensure zero-downtime rollout.
The expand-and-contract pattern allows new and old application versions to read/write concurrently during deployment by making non-breaking incremental schema changes.
Executing breaking database schema changes during live migration disrupts legacy application instances.

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