A global logistics organization is establishing an automated Infrastructure as Code (IaC) deployment pipeline to provision a transactional relational database handling order processing across North America and Europe. The workload requires multi-continent scale with strict ACID transaction guarantees. Security governance mandates that encryption keys must be managed through a centralized cloud key management service rather than requiring client applications to transmit raw key material during API operations. Additionally, the engineering team requires that the IaC state configuration prevents concurrent modification conflicts and supports state recovery. Which combination of database service, key management model, and IaC state storage best satisfies these requirements?
- Provision Cloud Spanner configured with Customer-Managed Encryption Keys (CMEK) stored in Cloud KMS, and configure the Terraform remote backend using a Cloud Storage bucket with object versioning and state locking enabled.Cevap
- BProvision Cloud SQL for PostgreSQL configured with Customer-Managed Encryption Keys (CMEK) stored in Cloud KMS, and store the Terraform state file in a Cloud Storage bucket with object versioning enabled.
- CProvision Cloud Spanner configured with Customer-Supplied Encryption Keys (CSEK) provided in each API header, and maintain the Terraform state file locally within a shared version-controlled Git repository.
- DProvision Cloud Spanner configured with Customer-Managed Encryption Keys (CMEK) stored in Cloud KMS, and store the Terraform state in an unversioned Cloud Storage bucket without state locking.