A healthcare organization operating in a single Google Cloud region needs to deploy a relational database layer for its patient billing application. The system requires full ACID transactional support, standard ANSI SQL capability, automatic regional high availability failover, and data encryption using customer-managed encryption keys (CMEK) integrated with Cloud KMS. The database dataset size is expected to remain around 400 GB with moderate query volume. The architectural team wants to optimize operational efficiency and minimize cost. Which storage and database design best satisfies these business and technical requirements?
- Deploy Cloud SQL for PostgreSQL configured with High Availability (regional failover) and encrypted with Customer-Managed Encryption Keys (CMEK) via Cloud KMS.Cevap
- BDeploy Cloud Spanner with a regional instance configuration using Google-managed encryption keys.
- CDeploy Cloud SQL for PostgreSQL with High Availability using Customer-Supplied Encryption Keys (CSEK) supplied at query runtime.
- DDeploy a Cloud Storage dual-region bucket using VPC Service Controls to host application data files and prevent exfiltration.
Cevap
Deploy Cloud SQL for PostgreSQL configured with High Availability (regional failover) and Customer-Managed Encryption Keys (CMEK) via Cloud KMS.
The correct solution uses Cloud SQL for PostgreSQL configured with High Availability (HA) and Customer-Managed Encryption Keys (CMEK). Cloud SQL supports standard ANSI SQL and ACID transactions for single-region relational workloads up to 64 TB. Configuring HA provides regional zero-data-loss synchronous replication across zones with automatic failover, and Cloud KMS integration provides CMEK encryption compliance.
Adım Adım Çözüm
Anahtar Kavram
Relational Database Selection (Cloud SQL vs. Cloud Spanner) and Security Governance