Examkin

Soru

Zorluk: ZorManaging Technology Debt and Legacy Cloud Migrations

A enterprise healthcare provider is migrating a legacy patient management platform from an on-premises data center to Google Cloud. The system consists of a monolithic application server tier coupled to an on-premises 15 TB MySQL database. The business requirement dictates a strict maximum downtime window of 2 hours during final cutover. Additionally, the application suffers from significant technical debt, specifically direct IP-based service addressing and hardcoded database endpoints.

To successfully mitigate the technical debt while meeting the strict downtime constraint, which TWO migration and operational strategies should the Cloud Architect recommend? (Select TWO.)

  1. Establish continuous binary log (binlog) CDC replication to Cloud SQL for MySQL using Database Migration Service for initial seed and online sync prior to cutover.Cevap
  2. Implement Cloud DNS Private Zones to replace hardcoded IP addresses with internal domain names across application configurations prior to cutover.Cevap
  3. C
    Migrate the relational database directly to Cloud Spanner to automatically resolve legacy stored procedure execution and scale multi-region transactions.
  4. D
    Order a Transfer Appliance to transfer the 15 TB database offline to Google Cloud to execute the final application cutover without using network bandwidth.

Cevap

The correct strategies are establishing continuous binary log replication to Cloud SQL using Database Migration Service and replacing hardcoded IP addresses with Cloud DNS Private Zones before cutover.
Continuous Change Data Capture (CDC) via binlog replication with Database Migration Service enables online synchronization of the 15 TB dataset, reducing the cutover process to a quick replication catch-up and primary promotion well under the 2-hour threshold. Concurrently, introducing Cloud DNS Private Zones remediates legacy networking technical debt by replacing static IP dependencies with manageable DNS records.

Adım Adım Çözüm

1
Analyze database migration downtime constraints
A 15 TB database cannot be migrated within a 2-hour window using offline import or one-time cold copy; continuous CDC replication is required.
Database Migration Service (DMS) leverages MySQL binlog replication to continuously sync deltas while the source remains active, allowing a near-zero downtime cutover.
2
Remediate networking technical debt
Decouple application configuration from physical host IP addresses using Cloud DNS Private Zones.
Hardcoded IP addresses prevent smooth DNS-based switchover and failover. Establishing private DNS endpoints resolves technical debt prior to shifting application instances.
3
Evaluate and eliminate non-viable architectural patterns
Reject Cloud Spanner migration and Transfer Appliance offline shipping.
Cloud Spanner introduces schema and query incompatibility for standard MySQL stored procedures, while Transfer Appliance cannot support continuous delta synchronization for a tight 2-hour cutover window.

Anahtar Kavram

Legacy Cloud Migration and Technical Debt Mitigation
Tahmini Süre:2m 30s
Bu soruyu puanla

Konular

Managing Technology Debt and Legacy Cloud Migrations

Bu konudan daha fazla soru