A digital health platform is designing its Google Cloud storage architecture to support two distinct workload requirements:
1. A transactional relational database for patient appointment scheduling operating strictly within a single GCP region that requires high availability across zones.
2. An initial migration of 2 petabytes of historical medical imaging records stored on-premises, where the existing 1 Gbps internet connection is heavily saturated during business hours.
Which two storage architecture decisions should the engineering team implement? (Select TWO answers.)
- Deploy Cloud SQL for PostgreSQL configured with High Availability (regional failover across two zones) for the appointment scheduling database.Answer
- BDeploy Cloud Spanner with a multi-region instance configuration for the appointment scheduling database.
- Order a Google Cloud Transfer Appliance to capture and physically ship the 2 petabytes of medical imaging data to Cloud Storage.Answer
- DConfigure Storage Transfer Service to stream the 2 petabytes of medical imaging data over the existing 1 Gbps internet connection.
Answer
The architecture team should deploy Cloud SQL for PostgreSQL configured with High Availability for the single-region appointment database, and order a Google Cloud Transfer Appliance to perform the offline migration of the 2 petabyte imaging dataset.
Cloud SQL for PostgreSQL configured with High Availability delivers automated cross-zone failover within a single region for relational OLTP workloads. Google Cloud Transfer Appliance is the optimal solution for transferring multi-petabyte datasets offline when network bandwidth is constrained.
Step-by-Step Solution
Key Concept
Selecting GCP database and migration resources based on regional transaction requirements, relational model fit, and data transfer network constraints.