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 PL
Mob_nav_barsMENU

Google Exam Professional-Cloud-DevOps-Engineer 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:

Submit Cancel
Kanisha
7 days 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
8 days 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
11 days 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
...
Ma
20 days ago
D is the way to go! A Job resource with Terraform is the perfect solution to avoid configuration drift.
upvoted 0 times
Yuonne
4 days ago
It's important to follow Google-recommended practices when managing cloud resources for applications in GKE.
upvoted 0 times
...
Margart
12 days ago
I agree, using a Job resource with Terraform is a great way to ensure infrastructure as code reconciles periodically.
upvoted 0 times
...
...
Leatha
1 months 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
1 months ago
I'm not sure, I think option B) Configure Cloud Build with Terraform builder could also work well.
upvoted 0 times
...
Leslie
1 months 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
13 days ago
User 2: Yeah, I agree. It's a good choice to ensure infrastructure as code reconciles periodically.
upvoted 0 times
...
Jannette
17 days ago
User 1: B sounds good. Cloud Build is powerful and Terraform is great for managing infrastructure as code.
upvoted 0 times
...
...
Ronnie
1 months 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
18 days 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
1 months ago
A) Install and configure Config Connector in Google Kubernetes Engine (GKE).
upvoted 0 times
...
...
Annabelle
1 months ago
I agree with Jacklyn, Config Connector seems like the best choice to avoid configuration drift.
upvoted 0 times
...
Jacklyn
2 months ago
I think we should go with option A) Install and configure Config Connector in GKE.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77