An engineering team is configuring an automated CI/CD release pipeline for a web service deployed on Google Cloud Run using Terraform for infrastructure provisioning. The application relies on Cloud SQL for persistent data storage. Which TWO deployment and infrastructure management practices should the team implement to ensure release reliability and zero-downtime deployments?
- Perform database schema changes using multi-phase, backward-compatible updates before deploying new application code.Answer
- Configure Cloud Storage with object versioning as a remote backend for storing Terraform state files.Answer
- CExecute destructive database schema migrations concurrently with deploying the new Cloud Run revision.
- DStore Terraform state files locally within the CI/CD pipeline runner local file system.
- EAssign the primitive Owner IAM role to the deployment service account to streamline pipeline permissions.
Answer
The team must perform database schema changes using multi-phase, backward-compatible updates before deploying new application code, and configure Cloud Storage with object versioning as a remote backend for storing Terraform state files.
Safe release management requires that database changes are backward-compatible so that both old and new application instances can run concurrently without errors during traffic migration. Additionally, reliable Infrastructure as Code deployments depend on centralized state management with locking and versioning enabled in Cloud Storage.
Step-by-Step Solution
Key Concept
Zero-downtime release management and Infrastructure as Code state management