An enterprise logistics corporation is modernizing an aging on-premises inventory tracking system to resolve severe technical debt. The current workload consists of a legacy monolithic web application running on custom-configured Linux virtual machines (VMs) and a single-region PostgreSQL database. Over years of operation, manual server configurations have caused severe configuration drift, while custom deployment scripts frequently break during release cycles.
The leadership team wants to migrate the system to Google Cloud over an upcoming weekend maintenance window. The primary objectives are to minimize ongoing server maintenance overhead, avoid unnecessary infrastructure costs, and prevent data exfiltration from staging storage buckets by authorized users. The organization already operates an active Partner Interconnect link to Google Cloud with abundant available bandwidth.
Which TWO architectural patterns should the Cloud Architect recommend to address the technical debt and fulfill the migration requirements? (Select TWO)
- Migrate the relational workload to Cloud SQL for PostgreSQL and establish continuous data replication using Database Migration Service (DMS) prior to final cutover.Answer
- BMigrate the database to Cloud Spanner to ensure multi-region horizontal scaling and global synchronous replication for the inventory system.
- Refactor the application into lightweight container images deployed to Cloud Run, and enforce a VPC Service Controls perimeter around Cloud Storage data landing buckets.Answer
- DOrder a Google Cloud Transfer Appliance to physically transport the initial database snapshot offline to Google Cloud prior to cutover.