A retail organization is migrating its regional order-processing application to Google Cloud. The application requires a relational database operating strictly within a single Google Cloud region, supporting standard SQL transactions, strong consistency, and automatic multi-zone failover. The expected data dataset size is 350 GB with a peak load of 2,500 operations per second. Additionally, corporate security policy dictates that encryption keys must be managed in Cloud KMS with key rotation controlled by the security team. Which database and key management solution should the cloud architect recommend?
- Deploy Cloud SQL for PostgreSQL configured with High Availability (multi-zone) and encrypted using Customer-Managed Encryption Keys (CMEK) via Cloud KMS.Cevap
- BDeploy a multi-region Cloud Spanner instance configured with Customer-Managed Encryption Keys (CMEK) via Cloud KMS.
- CDeploy Cloud SQL for PostgreSQL configured with High Availability (multi-zone) using Customer-Supplied Encryption Keys (CSEK) supplied in every API call.
- DDeploy Cloud SQL for PostgreSQL using basic IAM database authentication alone, assuming IAM permissions sufficiently prevent unauthorized data egress to external Google Cloud Storage buckets.
Cevap
Deploy Cloud SQL for PostgreSQL configured with High Availability (multi-zone) and encrypted using Customer-Managed Encryption Keys (CMEK) via Cloud KMS.
Cloud SQL for PostgreSQL with High Availability provides a fully managed relational database with multi-zone redundancy tailored for single-region workloads. Utilizing Customer-Managed Encryption Keys (CMEK) integrated with Cloud KMS fulfills security requirements for customer control over key lifecycles without raw key handling overhead.
Adım Adım Çözüm
Anahtar Kavram
Selecting Cloud SQL HA vs Cloud Spanner for regional relational workloads and integrating CMEK