A healthcare provider is designing the backend database architecture for a patient scheduling system hosted in a single Google Cloud region. The application requires a fully managed relational database supporting standard SQL queries and ACID transactions, with automatic failover across zones to ensure high availability. The compliance team mandates that encryption keys for data at rest must be stored and rotated in Google Cloud KMS without requiring the operations team to manage raw key material directly. Which database architecture should you recommend to meet these technical and compliance requirements with minimal operational cost?
- Provision a Cloud SQL database instance in High Availability (HA) configuration encrypted with Customer-Managed Encryption Keys (CMEK) stored in Cloud KMS.Answer
- BProvision a multi-region Cloud Spanner instance encrypted with Customer-Managed Encryption Keys (CMEK) stored in Cloud KMS.
- CProvision a Cloud SQL database instance in High Availability (HA) configuration using Customer-Supplied Encryption Keys (CSEK) provided at instance creation.
- DProvision a single-zone Cloud SQL instance and configure continuous backup exports to Cloud Storage protected by standard IAM bucket permissions.
Answer
Provision a Cloud SQL database instance in High Availability (HA) configuration encrypted with Customer-Managed Encryption Keys (CMEK) stored in Cloud KMS.
The correct answer recommends Cloud SQL configured for High Availability (HA) paired with Customer-Managed Encryption Keys (CMEK) via Cloud KMS. Cloud SQL HA provisions primary and standby instances in separate zones within a single region, satisfying the requirement for automatic cross-zone failover and standard relational SQL ACID transactions. Utilizing CMEK fulfills compliance and key management requirements by storing keys in Cloud KMS without forcing the operations team to handle raw key material.
Step-by-Step Solution
Key Concept
Selecting Cloud SQL HA with CMEK for Regional Relational Workloads