Google Professional Cloud Architect
Get started today
Ultimate access to all questions.
You have implemented a continuous deployment pipeline that automatically deploys source code changes to your cloud infrastructure within instance groups designed for self-healing. After deploying a recent change, you notice a significant negative impact on a key performance indicator (KPI). Resolving the issue through investigation could take up to a week. What should you do to quickly mitigate the negative impact?
Exam-Like
A
Log in to a server, and iterate on the fix locally
B
Revert the source code change, and rerun the deployment pipeline
C
Log into the servers with the bad code change, and swap in the previous code
D
Change the instance group template to the previous one, and delete all instances
Explanation:
The most efficient way to mitigate the negative impact on the KPI is to revert the source code change and rerun the deployment pipeline (Option B). This approach ensures that the previous stable version of the code is redeployed automatically, preserving the integrity of the deployment pipeline and providing a clear audit trail in the source repository. While Option D is also technically correct, it involves manual intervention in the infrastructure, which is less efficient and less aligned with best practices for automated deployments. Therefore, Option B is the preferred solution.
Comments
Loading comments...