An enterprise is implementing a automated cloud infrastructure deployment pipeline on Google Cloud for a global transactional database and operational storage architecture. The technical requirements specify a relational database engine capable of handling multi-region transactions with external consistency across continents. Furthermore, the Infrastructure as Code (IaC) deployment pipeline using Terraform must guarantee concurrency safety and state recovery against corrupted or conflicting parallel executions. Which TWO architecture and provisioning strategies should be implemented to satisfy these requirements?
- Provision a Cloud Spanner multi-region instance configuration to support globally distributed relational transactions with strong consistency.Cevap
- Configure the Terraform backend using a Google Cloud Storage bucket with object versioning enabled and native state locking.Cevap
- CProvision a multi-region Cloud SQL for PostgreSQL instance with Customer-Supplied Encryption Keys (CSEK) to support global multi-master write operations.
- DStore the Terraform state files inside an unversioned local directory within the CI/CD worker container image to maintain high-speed pipeline state access.
Cevap
The correct architecture requires provisioning a Cloud Spanner multi-region instance for global relational ACID transactions and configuring a Cloud Storage backend with object versioning and state locking for Terraform state management.
Provisioning Cloud Spanner satisfies the requirement for multi-region relational database transactions with external consistency. Additionally, using Cloud Storage with versioning and state locking for the Terraform remote backend ensures safe concurrent deployment pipeline execution without state corruption.
Adım Adım Çözüm
Anahtar Kavram
Multi-region database provisioning and IaC remote state locking
Tahmini Süre:3m 0s