Google Professional Cloud DevOps Engineer Question 17
Single answerGoogle Cloud PlatformYour organization manages its infrastructure using Terraform. You are tasked with deploying a new Google Cloud project and ensuring that all resources adhere to the company’s compliance policies, which are defined as configuration templates. Additionally, the deployment must integrate with the existing CI/CD pipeline to automate future updates to the infrastructure. Which approach should you take to achieve this?
- A
Use Terraform to define the infrastructure as code and store the configuration in a version-controlled repository. Integrate the repository with the CI/CD pipeline to validate and apply changes automatically.
- B
Manually deploy the required resources using the Google Cloud Console, then export the configuration to Terraform for version control.
- C
Use Helm to define the infrastructure templates and deploy the resources to Google Cloud. Link Helm charts with the CI/CD pipeline for updates.
- D
Leverage the Cloud Foundation Toolkit to deploy pre-validated solutions and manually integrate each deployment into the CI/CD pipeline.
Show answer and explanation
Correct answer: A
Explanation
Using Terraform as an infrastructure-as-code tool is the best practice for managing Google Cloud resources at scale. It enables you to define infrastructure in a declarative format, ensuring compliance and repeatability. By storing Terraform configurations in a version control system, you can track changes and collaborate effectively. Integrating Terraform with a CI/CD pipeline automates the application of changes, reducing manual effort and ensuring consistency across environments.
- A. Correct.
This is the correct approach. Using Terraform to define the infrastructure as code ensures compliance and consistency. Storing configurations in version control enables collaboration and auditability, while integrating with the CI/CD pipeline automates validation and deployment processes.
- B. Incorrect.
This is not a recommended approach. Manually deploying resources increases the risk of human error and does not align with best practices for infrastructure as code or automation.
- C. Incorrect.
Helm is primarily used for managing Kubernetes applications, not for provisioning Google Cloud infrastructure. This makes it unsuitable for the scenario described.
- D. Incorrect.
While the Cloud Foundation Toolkit provides pre-validated templates, manually integrating deployments into the CI/CD pipeline adds unnecessary overhead and reduces automation.