A global healthcare provider is modernizing a legacy patient scheduling monolithic application to resolve architectural technical debt during its migration from an on-premises data center to Google Cloud. The application relies on an on-premises PostgreSQL relational database and stateless HTTP web microservices. The migration plan requires continuous database replication with near-zero downtime cutover and safe zero-downtime database schema evolutionary updates. Which TWO architectural and migration strategy patterns should the cloud architect recommend? (Select TWO.)
- Implement the expand-and-contract (parallel change) pattern for database schema changes to support both legacy and modernized application code simultaneously.Cevap
- BProvision Google Kubernetes Engine (GKE) cluster nodes to host the simple stateless HTTP microservices to optimize operational management.
- Use Database Migration Service (DMS) with continuous Change Data Capture (CDC) to synchronize the on-premises PostgreSQL database to Cloud SQL prior to final cutover.Cevap
- DImplement Customer-Supplied Encryption Keys (CSEK) for all migrated storage assets to meet security governance standards without external key management services.
Cevap
The correct recommendations are implementing the expand-and-contract pattern for schema migrations and utilizing Database Migration Service with CDC for minimal downtime database replication.
Database Migration Service (DMS) with CDC provides continuous replication to Cloud SQL with minimal downtime during cutover. Pairing this with the expand-and-contract database migration pattern enables backward compatibility, allowing legacy and modernized applications to interact with the database safely during incremental rollout phases.
Adım Adım Çözüm
Anahtar Kavram
Managing Technology Debt and Legacy Cloud Migrations via CDC replication and expand-and-contract schema migrations