New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

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?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Judy
9 hours ago
I prefer option B. Cloud Build with Terraform sounds efficient for CI/CD.
upvoted 0 times
...
Louisa
6 days ago
I think option A is the best choice. Config Connector integrates well with GKE.
upvoted 0 times
...
Desirae
11 days ago
Wait, we can use Terraform directly in GKE? That's cool!
upvoted 0 times
...
Glory
16 days ago
D) makes sense, but isn't it overkill for simple tasks?
upvoted 0 times
...
Malinda
21 days ago
C) seems a bit off, using a Pod for this?
upvoted 0 times
...
Candra
26 days ago
I think B) is better for CI/CD integration.
upvoted 0 times
...
Herschel
1 month ago
A) Config Connector is the way to go for GKE!
upvoted 0 times
...
Rutha
1 month 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
1 month 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
2 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
2 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
2 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
2 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
2 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
2 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
3 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
3 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
3 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
3 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
...

Save Cancel