Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise organization wants to streamline infrastructure provisioning on Google Cloud while eliminating manual interventions. Currently, engineers execute terraform apply directly from their local workstations, leading to configuration drift and inconsistent environments between staging and production.
The cloud architecture team establishes the following governance and operational requirements:
dev environment prior to promotion to prod.How should you design this automated provisioning workflow?
gcloud deployment-manager deployments create manually using deployment previews.This option suggests converting existing Terraform configurations to Google Cloud Deployment Manager templates and relying on developers to execute manual deployment commands using the Cloud SDK CLI.
dev to prod.Deployment Manager were the strategic forward-looking tool and the organization strictly mandated client-side manual deployments without CI/CD.
main branch that executes terraform plan and terraform apply -auto-approve simultaneously against both development and production projects whenever a commit is pushed.This approach configures a single branch (main) in Git to execute terraform plan and immediately execute terraform apply -auto-approve across both development and production environments simultaneously.
dev environment prior to being promoted to prod. Applying changes concurrently to both environments eliminates the safety barrier of pre-production validation.terraform plan and terraform apply in a single uninterrupted pipeline run on branch push bypasses the pull request review process, preventing engineers from inspecting the execution plan before infrastructure modifications occur.The organization maintained only a single ephemeral sandbox environment with no separation between development and production tiers.
terraform plan for automated validation, and configure branch triggers so merging into dev applies changes to the development environment, followed by merging dev into prod to apply changes to production.A GitOps infrastructure workflow uses a version-controlled Git repository as the single source of truth for infrastructure configuration, paired with automated CI/CD tools such as Cloud Build to execute Terraform commands predictably and reliably across environments.
terraform plan. Collaborators can inspect the generated execution plan directly on the pull request before any code is merged, preventing unintended changes from entering the codebase.dev to prod): Merging approved pull requests into the dev branch triggers a Cloud Build job that executes terraform apply against the development environment. Once verified in dev, a subsequent pull request merges the dev branch into prod, triggering an automated terraform apply in the production environment.
terraform plan) and validated against policies before actuation.This architecture adheres to Google Cloud's recommended GitOps blueprint for Infrastructure as Code. It establishes strict environment isolation, prevents configuration drift, and ensures changes are validated before impacting production workloads.
This approach relies on maintaining Terraform state files locally on engineers' workstations and attempting to transfer state files to CI/CD runners via SSH at build time.
dev and prod.Terraform was strictly used as a single-user CLI tool for local experimentation where no team collaboration or automation was needed.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated