Google Professional Cloud DevOps Engineer Exam - Topic 5 Question 99 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam

Question #: 99
Topic #: 5

[All Professional Cloud DevOps Engineer Questions]

[Building and implementing CI/CD pipelines for a service]

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?

AInstall and configure Config Connector in Google Kubernetes Engine (GKE).

BConfigure Cloud Build with a Terraform builder to execute plan and apply commands.

CCreate a Pod resource with a Terraform docker image to execute terraform plan and terraform apply commands.

DCreate a Job resource with a Terraform docker image to execute terraforrm plan and terraform apply commands.

Show Suggested Answer

Suggested Answer: A

by Viola at Nov 21, 2025, 09:15 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud DevOps Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Margret

22 days ago

I’m leaning towards option C. Pods are great, but I worry about resource management.

upvoted 0 times

...

Renato

27 days ago

Option B is solid. Terraform's plan and apply in Cloud Build can streamline deployments.

upvoted 0 times

...

Lucina

1 month ago

I feel option A is more aligned with Google practices. It automates everything nicely.

upvoted 0 times

...

Stephaine

1 month ago

Option D seems interesting. Jobs can handle tasks well, but is it the best for drift?

upvoted 0 times

...

Judy

2 months ago

I prefer option B. Cloud Build with Terraform sounds efficient for CI/CD.

upvoted 0 times

...

Louisa

2 months ago

I think option A is the best choice. Config Connector integrates well with GKE.

upvoted 0 times

...

Desirae

2 months ago

Wait, we can use Terraform directly in GKE? That's cool!

upvoted 0 times

...

Glory

2 months ago

D) makes sense, but isn't it overkill for simple tasks?

upvoted 0 times

...

Malinda

3 months ago

C) seems a bit off, using a Pod for this?

upvoted 0 times

...

Candra

3 months ago

I think B) is better for CI/CD integration.

upvoted 0 times

...

Herschel

3 months ago

A) Config Connector is the way to go for GKE!

upvoted 0 times

...

Rutha

3 months ago

B looks good, but I think the Job resource in D is a cleaner solution. Keeps the infrastructure code separate from the CI/CD pipeline.

upvoted 0 times

...

Mabel

3 months ago

Haha, I bet the developers are going to love having to write Terraform code. At least it's better than manually creating resources in the console.

upvoted 0 times

...

Sophia

3 months ago

I feel like creating a Job resource with a Terraform image could work, but I'm not confident if that's the right approach for periodic reconciliation.

upvoted 0 times

...

Juan

4 months ago

I think using Cloud Build with Terraform sounds familiar. We practiced a similar question about CI/CD pipelines, but I can't recall the exact steps.

upvoted 0 times

...

Luis

4 months ago

I like the idea of giving developers the ability to manage infrastructure as code. Option B with Cloud Build and Terraform seems like a straightforward way to do that while still maintaining control and following best practices. I think that's the way I'll go on this one.

upvoted 0 times

...

Vallie

4 months ago

I remember we discussed how Config Connector integrates with GKE, but I'm not entirely sure if it's the best choice for managing infrastructure as code.

upvoted 0 times

...

Justine

4 months ago

Hmm, I'm not too familiar with Config Connector, but option A seems like it could be a good solution to ensure infrastructure as code reconciles periodically. I'll need to look into how that works in more detail.

upvoted 0 times

...

Tawny

4 months ago

D is the correct answer. Using a Job resource is the way to go for executing Terraform commands in a reliable and scalable way.

upvoted 0 times

...

Dalene

5 months ago

Option A seems like the way to go. Config Connector is the recommended approach for managing infrastructure as code in GKE.

upvoted 0 times

...

Sharita

5 months ago

I vaguely remember that using a Pod resource might not be ideal for this scenario. We should focus on something that ensures ongoing compliance with infrastructure changes.

upvoted 0 times

...

Harrison

5 months ago

I'm a bit confused about the differences between options C and D. Both involve using a Terraform Docker image, but one is a Pod and the other is a Job. I'll need to research the pros and cons of each to decide which one is better for this scenario.

upvoted 0 times

...

Rima

5 months ago

I think option B sounds like the best approach here. Using Cloud Build with a Terraform builder would let the developers manage infrastructure as code while still following Google's recommended practices.

upvoted 0 times