Google Professional Cloud DevOps Engineer Question 189
Select 3Google Cloud PlatformYou are a DevOps Engineer at a company that wants to implement a new infrastructure setup on Google Cloud for their microservices-based application. The company requires infrastructure changes to be repeatable, maintainable, and consistent across environments (development, staging, production). Which of the following steps align with Google-recommended practices and blueprints for making infrastructure changes?
- A
Use Infrastructure as Code (IaC) tools like Terraform to define and manage infrastructure.
- B
Manually configure resources using the Google Cloud Console for each environment.
- C
Store IaC configuration files in a version-controlled repository, such as Git.
- D
Use Google Cloud Deployment Manager for infrastructure definitions and avoid any version control.
- E
Create reusable modules or templates for common infrastructure components.
Show answer and explanation
Correct answers: A, C, E
Explanation
Google-recommended practices for making infrastructure changes emphasize automation, repeatability, and maintainability. Using IaC tools, version control, and reusable components ensures that infrastructure changes can be consistently applied across environments and easily maintained over time.
- A. Correct.
Using Infrastructure as Code (IaC) tools like Terraform aligns with Google-recommended practices as it allows for automated and repeatable infrastructure management.
- B. Incorrect.
Manually configuring resources is not repeatable or scalable and is prone to errors, making it unsuitable for modern DevOps practices.
- C. Correct.
Storing IaC configuration files in a version-controlled repository is a best practice as it ensures change tracking, collaboration, and rollback capabilities.
- D. Incorrect.
While Google Cloud Deployment Manager is a valid tool for defining infrastructure, avoiding version control goes against best practices for managing infrastructure changes.
- E. Correct.
Creating reusable modules or templates for common infrastructure components improves consistency and reduces duplication, aligning with Google-recommended practices.