PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #28
You are designing a payments processing application on Google Cloud. The application must continue to serve requests and avoid any user disruption if a regional failure occurs. You need to use…
The correct answer is A. Use Cloud Spanner with a customer-managed encryption key (CMEK). Two requirements drive this answer: (1) regional failure resilience and (2) customer-managed encryption keys (CMEK). Cloud Spanner in a multi-region configuration provides automatic, transparent failover across regions with strong consistency - satisfying the 'continue to serve…
Question
You are designing a payments processing application on Google Cloud. The application must continue to serve requests and avoid any user disruption if a regional failure occurs. You need to use AES-256 to encrypt data in the database, and you want to control where you store the encryption key. What should you do?
Options
- AUse Cloud Spanner with a customer-managed encryption key (CMEK).
- BUse Cloud Spanner with default encryption.
- CUse Cloud SQL with a customer-managed encryption key (CMEK).
- DUse Bigtable with default encryption.
How the community answered
(47 responses)- A79% (37)
- B6% (3)
- C2% (1)
- D13% (6)
Explanation
Two requirements drive this answer: (1) regional failure resilience and (2) customer-managed encryption keys (CMEK). Cloud Spanner in a multi-region configuration provides automatic, transparent failover across regions with strong consistency - satisfying the 'continue to serve requests during regional failure' requirement. Cloud Spanner also supports CMEK, letting you control where the encryption key is stored (e.g., in Cloud KMS). Option B (default encryption) removes key control. Option C (Cloud SQL with CMEK) doesn't survive regional failures natively - Cloud SQL is regional, not multi-regional. Option D (Bigtable) uses default encryption with no customer key control.
Topics
Community Discussion
No community discussion yet for this question.