Examkin

Soru

Zorluk: OrtaManaging Technology Debt and Legacy Cloud Migrations

A global logistics and freight management company is modernizing its on-premises dispatch tracking system to Google Cloud to resolve significant architectural technical debt. The legacy system relies on microservices accessing a shared 20 TB MySQL database directly, causing tight coupling and schema migration failures. The business demands zero downtime during migration and a decoupled architecture moving forward.

Which of the following architectural actions should the cloud architect recommend to mitigate technical debt and execute the migration successfully? (Select TWO.)

  1. Use Database Migration Service (DMS) with continuous change data capture (CDC) to sync to Cloud SQL for MySQL, and utilize the expand-and-contract pattern to decouple application deployments from schema changes.Cevap
  2. Refactor application microservices to communicate via REST APIs and Cloud Pub/Sub asynchronous messaging instead of querying shared database tables directly.Cevap
  3. C
    Order a Google Cloud Transfer Appliance to perform an offline bulk copy of the 20 TB database, followed by immediate blue-green deployment with non-backwards-compatible schema changes.
  4. D
    Migrate the database to Cloud Spanner to handle standard relational workloads, and host stateless web microservices on Google Kubernetes Engine (GKE) with dedicated node pools.

Cevap

The correct recommendations are using Database Migration Service with continuous CDC replication combined with the expand-and-contract pattern, and refactoring microservices to communicate via APIs and Cloud Pub/Sub messaging instead of accessing shared database tables directly.
To manage technical debt during cloud migration, legacy shared database dependencies must be eliminated by introducing API layers and event messaging (Cloud Pub/Sub). Additionally, migrating live data with Database Migration Service using CDC alongside an expand-and-contract schema strategy enables zero-downtime migration and safe schema evolution.

Adım Adım Çözüm

1
Evaluate data migration and schema coupling strategies.
Database Migration Service (DMS) provides zero-downtime continuous replication from on-premises MySQL to Cloud SQL. Applying the expand-and-contract pattern ensures backwards-compatible schema changes during transition.
This resolves legacy schema coupling debt while maintaining zero downtime during migration.
2
Address service coupling and database access technical debt.
Decoupling services by introducing API endpoints and Cloud Pub/Sub event streams removes direct database sharing between microservices.
This establishes clear service boundaries and prevents cross-service database locks and rigid dependencies.

Anahtar Kavram

Managing Technical Debt and Decoupling Legacy Cloud Migrations
Bu soruyu puanla

Konular

Managing Technology Debt and Legacy Cloud Migrations

Bu konudan daha fazla soru