Google Professional Cloud DevOps Engineer Exam - Topic 2 Question 40 Discussion

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

Question #: 40
Topic #: 2

[All Professional Cloud DevOps Engineer Questions]

Your team of Infrastructure DevOps Engineers is growing, and you are starting to use Terraform to manage infrastructure. You need a way to implement code versioning and to share code with other team members. What should you do?

AStore the Terraform code in a version-control system. Establish procedures for pushing new versions and merging with the master.

BStore the Terraform code in a network shared folder with child folders for each version release. Ensure that everyone works on different files.

CStore the Terraform code in a Cloud Storage bucket using object versioning. Give access to the bucket to every team member so they can download the files.

DStore the Terraform code in a shared Google Drive folder so it syncs automatically to every team member's computer. Organize files with a naming convention that identifies each new version.

Show Suggested Answer

Suggested Answer: A

by Gayla at May 03, 2022, 01:08 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

Christene

5 months ago

Wait, are we really considering B? That sounds messy.

upvoted 0 times

...

Charlene

5 months ago

A is the standard practice, can't go wrong there!

upvoted 0 times

...

Maurine

5 months ago

D sounds convenient, but is it really secure?

upvoted 0 times

...

Markus

5 months ago

I disagree, C could work if set up right.

upvoted 0 times

...

Whitley

5 months ago

A is definitely the best option for version control.

upvoted 0 times

...

Haley

5 months ago

I feel like using Google Drive for syncing is convenient, but it doesn't really provide version control. Option D seems too informal for managing infrastructure code. I think we should stick with something more robust like option A.

upvoted 0 times

...

Teddy

5 months ago

I vaguely recall something about using cloud storage for versioning, but I’m not clear on how effective that would be for collaboration. Option C might work, but I feel like it lacks the structure of a version-control system.

upvoted 0 times

...

India

5 months ago

I think we did a practice question where storing code in a shared folder was mentioned, but it was more about collaboration. Option B sounds risky since it could lead to conflicts if everyone is working on different files.

upvoted 0 times

...

Carylon

5 months ago

I remember we discussed the importance of using a version-control system for managing code. Option A seems like the best practice, but I'm not entirely sure about the merging procedures.

upvoted 0 times

...

Rolland

6 months ago

Hmm, this seems like a tricky one. I'll need to think through the relationship between LINE_BREAKER and SHOULD_LINEMERGE to figure out the right answer.

upvoted 0 times

...

Denna

6 months ago

Okay, let's think this through step-by-step. We need a managed MongoDB environment with SLA support, and the question specifically mentions Google Kubernetes Engine. That rules out the Compute Engine and Managed Instance Group options. I'm leaning towards the MongoDB Alias from the Marketplace, but I'll double-check the other choices just to be sure.

upvoted 0 times

...

Marylin

6 months ago

This looks like a MPLS TE question. I think the key is to understand how to route traffic over a specific tunnel, so I'll focus on the options related to that.

upvoted 0 times

...

Susana

6 months ago

Okay, let me think this through. I know the golden image needs to be updated when there are changes to the application or the underlying base image. I'll make sure to check all the options carefully.

upvoted 0 times

...