You created a pipeline that can deploy your source code changes to your infrastructure in instance groups for self-healing. One of the changes negatively affects your key performance indicator. You ar

The correct answer is B. Revert the source code change, and rerun the deployment pipeline. There is no explicit command for rolling back an update to a previous version, but if you decide to roll back an update (either a fully committed update or a canary update), you can do so by making a new update request and passing in the instance template that you want to roll ba

Submitted by valeria.br· Mar 30, 2026Managing implementation

Question

You created a pipeline that can deploy your source code changes to your infrastructure in instance groups for self-healing. One of the changes negatively affects your key performance indicator. You are not sure how to fix it, and investigation could take up to a week. What should you do?

Options

ALog in to a server, and iterate on the fox locally
BRevert the source code change, and rerun the deployment pipeline
CLog into the servers with the bad code change, and swap in the previous code
DChange the instance group template to the previous one, and delete all instances

How the community answered

(23 responses)

A
17% (4)
B
74% (17)
C
4% (1)
D
4% (1)

Explanation

There is no explicit command for rolling back an update to a previous version, but if you decide to roll back an update (either a fully committed update or a canary update), you can do so by making a new update request and passing in the instance template that you want to roll back to. https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed- instance-groups#rolling_back_an_update

Topics

#CI/CD pipeline#deployment rollback#instance groups#release management

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-ARCHITECT Practice