Exam Professional Cloud DevOps Engineer All Questions

View all questions & answers for the Professional Cloud DevOps Engineer exam

Exam Professional Cloud DevOps Engineer topic 1 question 151 discussion

Actual exam question from Google's Professional Cloud DevOps Engineer

Question #: 151
Topic #: 1

[All Professional Cloud DevOps Engineer Questions]

Your company runs applications in Google Kubernetes Engine (GKE) that are deployed following a GitOps methodology. Application developers frequently create cloud resources to support their applications. You want to give developers the ability to manage infrastructure as code, while ensuring that you follow Google-recommended practices. You need to ensure that infrastructure as code reconciles periodically to avoid configuration drift. What should you do?

A. Install and configure Config Connector in Google Kubernetes Engine (GKE).
B. Configure Cloud Build with a Terraform builder to execute terraform plan and terraform apply commands.
C. Create a Pod resource with a Terraform docker image to execute terraform plan and terraform apply commands.
D. Create a Job resource with a Terraform docker image to execute terraform plan and terraform apply commands.

Show Suggested Answer

Suggested Answer: A 🗳️

by activist at Oct. 21, 2023, 11:03 p.m.

Comments

Submit Cancel

poplot321

4 months ago

Selected Answer: B

B is the correct answer here because it talks about GitOps and Infrastructure as Code without Kubernetes CRDs: https://cloud.google.com/docs/terraform/resource-management/managing-infrastructure-as-code If CRDs are mentioned, then it would be Config Connector: https://cloud.google.com/config-connector/docs/overview

upvoted 1 times

...

6a8c7ad

11 months, 1 week ago

B. So they can only create with pipeline.

upvoted 1 times

...

Xoxoo

1 year, 5 months ago

Selected Answer: A

Config Connector allows you to manage Google Cloud resources through Kubernetes-style declarative configuration. By installing and configuring Config Connector in GKE, you can define and manage cloud resources using Kubernetes manifests, ensuring that infrastructure configurations are reconciled periodically to avoid configuration drift

upvoted 2 times

...

xhilmi

1 year, 7 months ago

Selected Answer: A

Option A is the recommended approach for managing infrastructure as code and avoiding configuration drift in a Google Kubernetes Engine (GKE) environment while following Google-recommended practices. Config Connector is a Kubernetes extension that allows you to manage Google Cloud resources as Kubernetes objects. By installing and configuring Config Connector in GKE, you can declare your cloud resources as Kubernetes CustomResourceDefinitions (CRDs) and have them managed by Kubernetes controllers. This ensures that the desired state of your infrastructure is continuously reconciled with the actual state, helping to prevent configuration drift. Config Connector aligns with the GitOps methodology, providing a declarative way to manage cloud resources and maintain consistency in your environment.

upvoted 2 times

...

mshafa

1 year, 8 months ago

Selected Answer: A

Config Connector's controllers eventually reconcile your environment with your desired state. https://cloud.google.com/config-connector/docs/overview

upvoted 3 times

...

lelele2023

1 year, 8 months ago

Selected Answer: A

Why not A? https://cloud.google.com/blog/products/containers-kubernetes/anthos-config-management-config-controller-available-on-gke Config controller leverages config connector, config controller includes config-synct/gcp-cloud-resource-creation/policy-sync, it 'gitops', 'reconcile', 'taking-care-of-gcp-cloud-resource'

upvoted 2 times

lelele2023

1 year, 8 months ago

plus 'Google-recommended practices'

upvoted 1 times

...

Mar_Mar

1 year, 8 months ago

I also vote for B

upvoted 1 times

...

activist

1 year, 9 months ago

I think the answer B is correct.

upvoted 2 times

...