Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

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

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 plan and 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 terraforrm plan and terraform apply commands.

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

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 75
Topic #: 5
[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?

Show Suggested Answer Hide Answer
Suggested Answer: A

The best option to give developers the ability to manage infrastructure as code, while ensuring that you follow Google-recommended practices, is to install and configure Config Connector in Google Kubernetes Engine (GKE).

Config Connector is a Kubernetes add-on that allows you to manage Google Cloud resources through Kubernetes. You can use Config Connector to create, update, and delete Google Cloud resources using Kubernetes manifests. Config Connector also reconciles the state of the Google Cloud resources with the desired state defined in the manifests, ensuring that there is no configuration drift1.

Config Connector follows the GitOps methodology, as it allows you to store your infrastructure configuration in a Git repository, and use tools such as Anthos Config Management or Cloud Source Repositories to sync the configuration to your GKE cluster. This way, you can use Git as the source of truth for your infrastructure, and enable reviewable and version-controlled workflows2.

Config Connector can be installed and configured in GKE using either the Google Cloud Console or the gcloud command-line tool. You need to enable the Config Connector add-on for your GKE cluster, and create a Google Cloud service account with the necessary permissions to manage the Google Cloud resources. You also need to create a Kubernetes namespace for each Google Cloud project that you want to manage with Config Connector3.

By using Config Connector in GKE, you can give developers the ability to manage infrastructure as code, while ensuring that you follow Google-recommended practices. You can also benefit from the features and advantages of Kubernetes, such as declarative configuration, observability, and portability4.


1: Overview | Artifact Registry Documentation | Google Cloud

2: Deploy Anthos on GKE with Terraform part 1: GitOps with Config Sync | Google Cloud Blog

3: Installing Config Connector | Config Connector Documentation | Google Cloud

4: Why use Config Connector? | Config Connector Documentation | Google Cloud

by Marvel at Aug 22, 2024, 10:00 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Leontine
9 months ago
Wait, can you really use Terraform in a Pod? That’s new to me!
upvoted 0 times
...
Herman
9 months ago
D sounds interesting, but is it really the best practice?
upvoted 0 times
...
Twana
10 months ago
C seems a bit off, using a Pod for this?
upvoted 0 times
...
Nan
10 months ago
I think B is better for CI/CD workflows.
upvoted 0 times
...
Narcisa
10 months ago
A is the way to go for GKE integration!
upvoted 0 times
...
Helga
10 months ago
I’m leaning towards option A, but I’m a bit uncertain about how it handles drift compared to the others.
upvoted 0 times
...
Virgilio
11 months ago
I feel like creating a Job resource with Terraform could work, but I’m not confident if that’s the recommended approach for reconciliation.
upvoted 0 times
...
Wayne
11 months ago
I think using Cloud Build with Terraform sounds familiar. We practiced a similar question about CI/CD pipelines, right?
upvoted 0 times
...
Carline
11 months ago
I remember we discussed Config Connector in our study group, but I'm not entirely sure if it's the best fit for this scenario.
upvoted 0 times
...
Walton
11 months ago
I'm leaning towards option D. Creating a Job resource with a Terraform docker image to execute the plan and apply commands could be a good way to automate the infrastructure management process and avoid configuration drift.
upvoted 0 times
...
Filiberto
11 months ago
Hmm, I'm a bit confused on the best approach here. I know we need to give developers the ability to manage infrastructure as code, but I'm not sure which of these options would be the most effective in ensuring we follow Google-recommended practices.
upvoted 0 times
...
Ashleigh
11 months ago
This question seems straightforward. I think the key is to find a way to manage infrastructure as code while ensuring it reconciles periodically to avoid configuration drift, as the prompt states.
upvoted 0 times
...
Shaniqua
11 months ago
Based on the details provided, I'd say option A is the way to go. Installing and configuring Config Connector in GKE seems like the best solution to meet the requirements of managing infrastructure as code and ensuring periodic reconciliation.
upvoted 0 times
...
Dino
11 months ago
Okay, let me think this through step-by-step. The contract management process has pre-award, award, and post-award phases. Bid/no-bid and proposal prep are definitely seller activities, so they must be in the pre-award phase. I'll select A.
upvoted 0 times
...
Kip
11 months ago
I'm not entirely sure about Mr. Dixon. On one hand, he's friends with staff, which might count, but does that really line up with ‘own use'?
upvoted 0 times
...
Kanisha
2 years ago
You know, this question is making me hungry. I could really go for a nice terraform pie right about now.
upvoted 0 times
...
Kizzy
2 years ago
Hmm, I'm torn between A and D. But I guess I'd go with A. Config Connector just sounds more 'Google-y', you know?
upvoted 0 times
...
Jesse
2 years ago
C? Really? Manually running Terraform in a Pod? That's so 2010. Wake me up when you've got a real answer.
upvoted 0 times
Dyan
2 years ago
Yeah, using Config Connector or Cloud Build with Terraform integration would be a better approach.
upvoted 0 times
...
Yolande
2 years ago
D) Create a Job resource with a Terraform docker image to execute terraform plan and terraform apply commands.
upvoted 0 times
...
Amber
2 years ago
B) Configure Cloud Build with a Terraform builder to execute plan and apply commands.
upvoted 0 times
...
Joseph
2 years ago
A) Install and configure Config Connector in Google Kubernetes Engine (GKE).
upvoted 0 times
...
...
Ma
2 years ago
D is the way to go! A Job resource with Terraform is the perfect solution to avoid configuration drift.
upvoted 0 times
Zona
2 years ago
Cloud Build with a Terraform builder is another option to consider for executing plan and apply commands.
upvoted 0 times
...
Lindsey
2 years ago
Config Connector in GKE can also be a useful tool for managing infrastructure as code.
upvoted 0 times
...
Yuonne
2 years ago
It's important to follow Google-recommended practices when managing cloud resources for applications in GKE.
upvoted 0 times
...
Margart
2 years ago
I agree, using a Job resource with Terraform is a great way to ensure infrastructure as code reconciles periodically.
upvoted 0 times
...
...
Leatha
2 years ago
I think option D) Create a Job resource with a Terraform docker image might be a good alternative for periodic reconciliation.
upvoted 0 times
...
Lavonda
2 years ago
I'm not sure, I think option B) Configure Cloud Build with Terraform builder could also work well.
upvoted 0 times
...
Leslie
2 years ago
B sounds good to me. Cloud Build is super powerful, and using Terraform makes it easy to manage infrastructure as code.
upvoted 0 times
Samira
2 years ago
Yeah, I agree. It's a good choice to ensure infrastructure as code reconciles periodically.
upvoted 0 times
...
Jannette
2 years ago
B sounds good. Cloud Build is powerful and Terraform is great for managing infrastructure as code.
upvoted 0 times
...
...
Ronnie
2 years ago
A, definitely! Config Connector is the way to go for GitOps on GKE. It's like having your own personal infrastructure butler.
upvoted 0 times
Micaela
2 years ago
A, definitely! Config Connector is the way to go for GitOps on GKE. It's like having your own personal infrastructure butler.
upvoted 0 times
...
Cathrine
2 years ago
A) Install and configure Config Connector in Google Kubernetes Engine (GKE).
upvoted 0 times
...
...
Annabelle
2 years ago
I agree with Jacklyn, Config Connector seems like the best choice to avoid configuration drift.
upvoted 0 times
...
Jacklyn
2 years ago
I think we should go with option A) Install and configure Config Connector in GKE.
upvoted 0 times
...

Save Cancel