An enterprise operating strictly within a single GCP region needs to migrate an on-premises PostgreSQL database supporting an enterprise resource planning (ERP) system to Google Cloud. The workload requires full ACID compliance, complex relational SQL joins, automated cross-zone high availability failover, and support for up to 2,000 IOPS on a 600 GB database. The system does not require global read/write distribution or multi-region replication. Cost optimization and low operational overhead are primary business drivers. Which storage and database strategy should the Cloud Architect recommend?
- Deploy a Cloud SQL for PostgreSQL instance configured with High Availability (regional configuration across two zones) and dynamic storage growth enabled.Cevap
- BProvision a Cloud Spanner instance configured with a multi-region instance configuration to ensure maximum relational availability.
- CDeploy a single-zone Cloud SQL for PostgreSQL instance configured with Customer-Supplied Encryption Keys (CSEK) stored in application code to satisfy encryption compliance.
- DDeploy a single-zone Cloud SQL for PostgreSQL instance relying solely on granular IAM database user roles to prevent unauthorized data exfiltration to external Cloud Storage buckets.
Cevap
Deploy a Cloud SQL for PostgreSQL instance configured with High Availability (regional configuration across two zones) and dynamic storage growth enabled.
Cloud SQL for PostgreSQL configured with High Availability provisions a primary instance and a standby instance in two separate availability zones within the same region. Data is synchronously replicated to the standby persistent disk, enabling automated failover in the event of an outage. This fulfills all requirements for ACID transactions, complex joins, high availability, and performance while remaining cost-optimized for a single-region deployment.
Adım Adım Çözüm
Anahtar Kavram
Selecting Cloud SQL over Cloud Spanner for single-region relational database workloads
Tahmini Süre:2m 0s