Google Professional Cloud Network Engineer Exam - Topic 1 Question 16 Discussion

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

Question #: 16
Topic #: 1

[All Professional Cloud Network Engineer Questions]

You have an application that is running in a managed instance group. Your development team has released an updated instance template which contains a new feature which was not heavily tested. You want to minimize impact to users if there is a bug in the new template.

How should you update your instances?

AManually patch some of the instances, and then perform a rolling restart on the instance group.

BUsing the new instance template, perform a rolling update across all instances in the instance group. Verify the new feature once the rollout completes.

CDeploy a new instance group and canary the updated template in that group. Verify the new feature in the new canary instance group, and then update the original instance group.

DPerform a canary update by starting a rolling update and specifying a target size for your instances to receive the new template. Verify the new feature on the canary instances, and then roll forward to the rest of the instances.

Show Suggested Answer

Suggested Answer: D

https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups#starting_a_canary_update

https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups

by Corinne at May 09, 2022, 10:54 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Lea

4 months ago

I think D is the best choice for controlled rollout.

upvoted 0 times

...

Cecily

4 months ago

Wait, can you really trust the new feature if it wasn't heavily tested?

upvoted 0 times

...

Slyvia

4 months ago

But wouldn't a rolling update (Option B) be faster?

upvoted 0 times

...

Tamekia

4 months ago

I agree, canary testing is key for minimizing risks.

upvoted 0 times

...

Kristeen

5 months ago

Option C sounds like the safest bet!

upvoted 0 times

...

Junita

5 months ago

I recall that canary deployments are often recommended for untested features. Option C seems like the best choice to ensure we can test the new feature without affecting all users at once.

upvoted 0 times

...

Alecia

5 months ago

I practiced a similar question where we had to choose between rolling updates and canary releases. I think option B could work, but I’m worried about the lack of verification before the rollout.

upvoted 0 times

...

Geoffrey

5 months ago

I'm not entirely sure, but I feel like a rolling update might be risky if the new feature isn't well tested. Maybe option D would be safer?

upvoted 0 times

...

Mozelle

5 months ago

I remember we discussed the importance of minimizing user impact during updates. I think option C sounds like a good approach with the canary deployment.

upvoted 0 times

...

Louvenia

5 months ago

This seems straightforward. The attributes are provided by the target system, and the list can differ based on the application type. I'll make sure to look at the Match column to see which ones are selected.

upvoted 0 times

...

Margo

5 months ago

I've got a good feeling about the "Configure Properties of Change Request Step" option. That sounds like the right place to define SLAs by priority.

upvoted 0 times

...

Lenita

5 months ago

Okay, I've got this. The key here is to identify the attribute that poses the greatest risk for the requirements engineering process. I'll carefully evaluate each option.

upvoted 0 times

...