Google Exam Professional Cloud DevOps Engineer Topic 5 Question 82 Discussion

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

Question #: 82
Topic #: 5

[All Professional Cloud DevOps Engineer Questions]

You use Terraform to manage an application deployed to a Google Cloud environment The application runs on instances deployed by a managed instance group The Terraform code is deployed by using a CI/CD pipeline When you change the machine type on the instance template used by the managed instance group, the pipeline fails at the terraform apply stage with the following error message

You need to update the instance template and minimize disruption to the application and the number of pipeline runs What should you do?

ADelete the managed instance group and recreate it after updating the instance template

BAdd a new instance template update the managed instance group to use the new instance template and delete the old instance template

CRemove the managed instance group from the Terraform state file update the instance template and reimport the managed instance group.

DSet the create_bef ore_destroy meta-argument to true in the lifecycle block on the instance template

Show Suggested Answer

Suggested Answer: B

by Dominic at Oct 22, 2024, 09:46 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

Vallie

1 months ago

I'm just glad I'm not the one who has to figure this out on a production system. Can you imagine the angry calls from the users if we botch this update?

upvoted 0 times

Alonso

15 days ago

Then we can gradually replace the instances in the group with the new template to minimize disruption.

upvoted 0 times

...

Viva

19 days ago

We should create a new instance template with the updated machine type and update the managed instance group to use the new template.

upvoted 0 times

...

James

1 months ago

Haha, I bet the Terraform maintainers had a good laugh when they came up with that `create_before_destroy` meta-argument. Looks like that might be the way to go here, though I'd want to test it out first.

upvoted 0 times

Evette

4 days ago

Agreed. Let's make sure to test it thoroughly to minimize any potential issues with the pipeline.

upvoted 0 times

...

Leota

23 days ago

That sounds like a good idea. We should definitely test it out first before making any changes.

upvoted 0 times

...

Shoshana

1 months ago

We could try using the `create_before_destroy` meta-argument to update the instance template without disrupting the application.

upvoted 0 times

...

Fannie

2 months ago

Wait, so we can't just delete the managed instance group and recreate it? That seems like the simplest solution, but I guess it could cause downtime. Gotta love Terraform's idempotency!

upvoted 0 times

Pok

6 days ago

Deleting and recreating the managed instance group could work, but it might cause downtime for the application.

upvoted 0 times

...

Darci

25 days ago

Another option is to manually update the instance template and then trigger a rolling update on the managed instance group.

upvoted 0 times

...

Dortha

29 days ago

You could create a new instance template with the updated machine type and then update the managed instance group to use the new template.

upvoted 0 times

...

Filiberto

2 months ago

Ah, I see. The key here is to minimize disruption to the application while updating the instance template. I think option B might be the best approach, but I'll need to double-check the details.

upvoted 0 times

Marjory

1 months ago

User 2: Yeah, I agree. Updating the managed instance group to use the new instance template and then deleting the old one sounds like a good plan.

upvoted 0 times

...

Ceola

1 months ago

User 1: I think option B is the way to go. It seems like the least disruptive option.

upvoted 0 times

...

Jose

2 months ago

Why do you think D is the correct answer?

upvoted 0 times

...

Elbert

2 months ago

Hmm, this is a tricky one. I'm not sure I fully understand the issue with the instance template change causing the pipeline to fail. I'll need to carefully read through the options and think this through.

upvoted 0 times