A online gaming telemetry platform is establishing automated pre-deployment testing procedures on Google Cloud. The infrastructure is provisioned using Terraform and deploys containerized microservices onto private Google Kubernetes Engine (GKE) clusters. To prevent deployment failures during high-traffic game launches and enforce operational security, the cloud architecture team needs to validate solution readiness in the CI/CD pipeline prior to production release. Which TWO validation procedures should the cloud architect incorporate into the automated testing pipeline? (Select TWO.)
- Automate pre-flight quota checks by querying regional resource limits against anticipated peak capacity demands before executing infrastructure provisioning.Answer
- Configure the Cloud Storage remote backend for Terraform state files with Object Versioning and Object Locking enabled to prevent state corruption during automated runs.Answer
- CGrant the deployment service account the Service Account Admin role (roles/iam.serviceAccountAdmin) to allow the CI/CD runner to attach runtime identities to GKE nodes.
- DDisable GKE control plane authorized networks during the pre-flight testing phase to guarantee unconstrained API access for external CI/CD pipeline runners.
Answer
The validation procedures that should be incorporated into the automated testing pipeline are: automating pre-flight regional resource quota checks against peak capacity demands prior to provisioning, and configuring the Cloud Storage remote backend for Terraform with Object Versioning and Object Locking enabled.
Automating regional quota verification prevents resource allocation failures during deployment, while enforcing Object Versioning and Object Locking on the Terraform backend in Cloud Storage secures IaC state against race conditions and corruption.
Step-by-Step Solution
Key Concept
Technical Solution Testing and Validation Procedures