Examkin

Question

Difficulty: EasyManaging Technology Debt and Legacy Cloud Migrations

An organization is migrating a legacy monolithic web application to Google Cloud. To manage technical debt effectively without delaying the initial cloud adoption schedule, the enterprise wants to reduce operational overhead for database maintenance while avoiding unnecessary application rewrites during the first phase. Which TWO cloud migration strategies should the team adopt? (Select TWO.)

  1. Rehost the application virtual machines directly onto Compute Engine using Migrate for Compute Engine to minimize initial migration risk and application code changes.Answer
  2. Replatform the self-hosted single-region relational database to Cloud SQL to reduce operational maintenance debt without modifying the database schema.Answer
  3. C
    Refactor the legacy monolith immediately into a microservices architecture running on Google Kubernetes Engine (GKE) prior to the initial cloud cutover.
  4. D
    Migrate the single-region relational database directly to Cloud Spanner to ensure maximum future scalability.

Answer

The team should rehost the application virtual machines directly to Compute Engine to minimize initial migration risk, and replatform the self-hosted relational database to managed Cloud SQL to reduce operational maintenance debt.
The combination of rehosting virtual machines to Compute Engine and replatforming relational databases to Cloud SQL strikes an optimal balance between fast migration execution and reducing operational legacy debt. Rehosting minimizes application code changes, while Cloud SQL offloads database backups, patching, and administration to Google Cloud.

Step-by-Step Solution

1
Analyze the migration constraints and technical debt goals.
Identified the need to avoid application rewrites initially while reducing operational database overhead.
Choosing appropriate migration patterns (rehost vs. replatform vs. refactor) directly impacts migration timelines and technical debt management.
2
Evaluate application compute migration options.
Rehosting virtual machines on Compute Engine allows fast lift-and-shift without refactoring code.
Rehosting legacy VMs minimizes upfront risk and avoids introducing complex microservices refactoring during early phases.
3
Evaluate database migration options.
Replatforming to managed Cloud SQL eliminates operational management debt without requiring global multi-region database rewrites.
Cloud SQL provides managed relational features for single-region workloads without the architectural changes required by Cloud Spanner.

Key Concept

Managing Technical Debt with Pragmatic Cloud Migration Strategies (Rehost and Replatform)
Rate this question

Topics

Managing Technology Debt and Legacy Cloud Migrations

More questions from this topic